WO2014000179A1 - Procédé et dispositif de gestion de facturation - Google Patents

Procédé et dispositif de gestion de facturation Download PDF

Info

Publication number
WO2014000179A1
WO2014000179A1 PCT/CN2012/077617 CN2012077617W WO2014000179A1 WO 2014000179 A1 WO2014000179 A1 WO 2014000179A1 CN 2012077617 W CN2012077617 W CN 2012077617W WO 2014000179 A1 WO2014000179 A1 WO 2014000179A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
information
charging
operator
identification
Prior art date
Application number
PCT/CN2012/077617
Other languages
English (en)
Chinese (zh)
Inventor
吴先玉
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2012/077617 priority Critical patent/WO2014000179A1/fr
Priority to CN201280000552.1A priority patent/CN103650416A/zh
Publication of WO2014000179A1 publication Critical patent/WO2014000179A1/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
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/43—Billing software details
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/44—Augmented, consolidated or itemized billing statement or bill presentation

Definitions

  • the present invention relates to the field of communications, and in particular, to a charging management method and device.
  • the SDP Service Delivery Platform
  • the access gateway encapsulates the network capability and service support capability of the operator into a capability interface and is open to third parties.
  • the third party can invoke the SDP.
  • the capability interface uses the capabilities provided by the operator.
  • one operator corresponds to one SDP
  • the SDP stores the product price information of each product included in the operator
  • each interface in the SDP corresponds to one product price information, when the third party needs to call one of the SDPs.
  • the SDP obtains the product price information corresponding to the interface, obtains the charging information according to the price information of the product, and sends the charging information to the charging system of the operator.
  • each operator needs to build a corresponding SDP, which increases the operating cost of the operator. If the third party needs to use the capabilities of multiple operators, the third party needs to access each operator's SDP and call the corresponding one. The interface increases the cost of using third parties. Summary of the invention
  • the present invention provides a charging management method and device.
  • the technical solution is as follows:
  • a charging management method comprising:
  • the access gateway And receiving an authentication and charging request message sent by the access gateway, where the authentication and charging request message carries the user identifier and an identifier of the capability interface to be invoked;
  • a billing management device the device comprising:
  • a receiving module configured to receive an authentication and charging request message sent by the access gateway, where the authentication charging request message carries a user identifier and an identifier of the capability interface to be invoked;
  • An acquiring module configured to obtain, according to the corresponding relationship between the identifier of the stored capability interface, the identifier of the operator, and the product price information, the operator and the charging information to which the user corresponding to the user identifier belongs;
  • a sending module configured to send a charging request message to the charging system of the operator to which the user corresponding to the user identifier is located, where the charging request message carries the charging information, so that the charging system is configured according to the Billing information is charged.
  • the authentication and charging request message sent by the access gateway is received, where the authentication charging request message carries the user identifier and the identifier of the capability interface to be invoked, according to the identifier and operation of the stored capability interface. Corresponding relationship between the quotient identifier and the product price information, obtaining the operator and billing information to which the user corresponding to the user identifier belongs, and sending a deduction request message to the billing system of the operator to which the user corresponding to the user identifier belongs.
  • the charging request message carries the charging information, so that the charging system performs charging according to the charging information.
  • the SDP can support multiple operators, multiple operators share one SDP, reduce the cost of the carrier, and when the third party uses the capabilities of multiple operators, only need to call a capability interface corresponding to the capability on the SDP. , reduce the cost of using third parties.
  • FIG. 1 is a flowchart of a charging management method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of storing user information according to another embodiment of the present invention.
  • FIG. 3 is a flowchart of a charging management method according to another embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a charging management device according to another embodiment of the present invention. detailed description
  • an embodiment of the present invention provides a charging management method, including:
  • Step 101 The SDP receives an authentication and charging request message sent by the access gateway, where the authentication and charging request message carries a user identifier and an identifier of the capability interface to be called.
  • Step 102 The SDP obtains the operator and charging information to which the user corresponding to the user identifier belongs according to the identifier of the stored capability interface, the identifier of the operator, and the product price information.
  • the charging information includes at least an identifier of the charging object, a charging fee, and a currency unit.
  • Step 103 The SDP sends a deduction request message to the charging system of the operator to which the corresponding user belongs, and the deduction request message carries the obtained charging information.
  • step 102 may be specifically as follows:
  • the SDP determines, according to the user identifier, an identifier of an operator to which the user corresponding to the user identifier belongs.
  • the SDP obtains corresponding product price information, the obtained product price, from the identifier of the stored capability interface, the identifier of the operator, and the product price information according to the identifier of the capability interface to be invoked and the identifier of the operator.
  • the information includes at least a product price, a currency unit, and a charging policy, and the charging policy includes at least payer information and charging rules;
  • the SDP obtains an identifier of the charging object according to the paying party information included in the charging policy, and calculates a charging fee according to the product price and the charging policy.
  • step 1021 may be specifically:
  • the SDP determines the range of the user ID to which the user ID belongs, and obtains the operator corresponding to the user ID range.
  • the obtained operator is the operator to which the user corresponding to the user ID belongs.
  • the foregoing step 1023 may be specifically:
  • the SDP determines that the identifier of the charging object is the user identifier; if the charging party information included in the charging policy is a third party, the SDP determines the identifier of the charging object.
  • a third party's identification, and a billing fee based on the price of the product and the billing strategy.
  • the method further includes:
  • the SDP obtains corresponding user information according to the user identifier from the corresponding relationship between the stored user identifier and the user information, where the user information includes at least a user status, and the user status includes a normal status or a suspended status, and is verified according to the user status. If the verification is passed, the operation of acquiring the operator and the charging information to which the user corresponding to the user identifier belongs is performed.
  • the method further includes:
  • the SDP receives the user information synchronization request message sent by the information system of the operator, where the user information synchronization request message carries the user identifier and user information of the user of the operator, and the user information includes at least a user status, and the user status includes a normal status. Or a suspended state, storing the user ID and user information of the user.
  • the authentication and charging request message sent by the access gateway is received, where the authentication and charging request message carries the user identifier and the identifier of the capability interface to be invoked, according to the identifier of the stored capability interface, the operator.
  • the correspondence between the identifier and the product price information acquires the operator and billing information to which the user corresponding to the user identifier belongs, and the billing information
  • the information includes at least the identifier of the charging object, the charging fee, and the currency unit, and sends a charging request message to the charging system of the operator, and the charging request message carries the charging information.
  • the SDP can support multiple operators, multiple operators share one SDP, reduce the cost of the operator, and when the third party uses the capabilities of multiple operators, only one capability interface corresponding to the capability needs to be called on the SDP. , reduce the cost of using third parties.
  • the embodiment of the invention provides a charging management method.
  • the SDP includes an access gateway and a management platform.
  • the SDP can support multiple operators by using the charging management method.
  • the management platform can establish users according to the following procedures 201 and 202. Correspondence between the identifier and the user information, including:
  • Step 201 The information system of the operator sends a user information synchronization request message to the management platform, where the user information synchronization request message carries at least the user identifier and user information of the user belonging to the operator.
  • the user information includes at least a user status, and the user status includes a suspended status and a normal status.
  • Step 202 The management platform receives the user information synchronization request message, and establishes a correspondence between the user identifier and the user information.
  • the management platform may create a corresponding user database for each operator, and when the user information synchronization request message sent by the information system of an operator is received, the user identifier and user information of the user are established. Corresponding relationship, and then information about the correspondence between the established user identifier and the user information is stored in the user database corresponding to the operator.
  • the access gateway in the SDP encapsulates the network capability and/or service support capability of the operator into a capability interface, and the capability interface can open the network capability and/or service support capability of the operator to the third party.
  • the same network capability and/or service support capability provided by multiple operators corresponds to the same capability interface in the access gateway, and the technician establishes the identity of the capability interface and the identifier of the operator in the management platform in advance. Correspondence with product price information.
  • the product price information includes at least the product price, the currency unit, and the billing strategy.
  • the charging policy defines the payer information and charging rules.
  • the SDP can support multiple operators by using the foregoing method.
  • the method includes:
  • Step 301 The third party sends an interface call request message to the access gateway in the SDP, where the interface call request message carries the identifier of the third party, the identifier of the capability interface to be invoked, and the information to be sent, and the information to be sent includes the user identifier. And information content;
  • the third party is an SP (Service Provider) and/or a CP (Content).
  • SP Service Provider
  • CP Content provider
  • third parties can provide content and/or services to users, and users can use content and/or services provided by third parties.
  • the identifier of the capability interface to be invoked may be the name of the capability interface to be invoked, the information to be sent may be a short message or a multimedia message, and the capability interface to be invoked may be a short message service (Sms) for sending a short message. Message service) interface, etc.
  • SMS short message service
  • the information to be sent is used as the short message, and the capability interface to be invoked is taken as an example of the Sms interface.
  • the third party sends an interface call request message to the access gateway in the SDP, and the interface call request message carries the identifier IDA of the third party, the identifier sms of the Sms interface, and the short message to be sent, and the short message to be sent includes the user identifier. IDB and SMS content of the text message to be sent.
  • Step 302 The access gateway receives the call request message of the interface, and performs access authentication control and SLA (Service Level Agreement) policy control on the third party. After access authentication control and SLA policy control are performed on the third party, Sending an interface call response message to a third party;
  • SLA Service Level Agreement
  • Step 303 The access gateway sends an authentication and charging request message to the management platform in the SDP, where the authentication and charging request message carries the identifier of the third party, the user identifier, and the identifier of the capability interface to be invoked.
  • the access gateway extracts the user identifier from the information to be sent, and sends an authentication and charging request message to the management platform in the SDP, where the authentication and charging request message carries the identifier of the third party, the extracted user identifier, and the to-be-called The identity of the capability interface.
  • the access gateway After receiving the identifier ID of the third party, the identifier sms of the Sms interface, and the interface call request message of the short message to be sent, the access gateway performs access authentication control and SLA policy control on the third party, and accesses the third party.
  • the authentication control is passed and the SLA policy is passed
  • the user identifier IDB is extracted from the short message to be sent, and the authentication and charging request message is sent to the management platform, where the authentication and charging request message carries the identifier IDA of the third party and the extracted user identifier.
  • Step 304 The management platform receives the authentication and charging request message, obtains the user status of the user corresponding to the user identifier, and performs verification according to the user status. If the verification succeeds, the operation corresponding to the user corresponding to the user identifier is determined. Specifically, the management platform receives the authentication and charging request message, where the authentication and charging request message carries the user identifier and the identifier of the capability interface to be invoked, and obtains the correspondence between the user identifier and the user information according to the user identifier. Corresponding user information is verified according to the user status included in the user information. If the user status included in the user information is in a suspended state, the verification fails.
  • the verification succeeds, and the operator to which the user corresponding to the user identifier belongs is determined according to the user identifier. If the verification fails, the management platform ends the operation and sends an exception message to notify the third party.
  • Each operator corresponds to a user identifier range. When the user signs a contract with the operator, the operator assigns a user identifier to the user, and the user identifier is a user identifier in the range of the user identifier corresponding to the operator.
  • the management platform determines, according to the user identifier, the operation of the operator to which the user corresponding to the user identifier belongs, which may be specifically: the management platform determines the range of the user identifier to which the user identifier belongs, and further obtains the operation corresponding to the user identifier range.
  • the carrier obtained by the operator is the operator to which the user corresponding to the user ID belongs.
  • the operator that the user corresponding to the user identifier belongs to may be determined according to the user identifier, and the corresponding relationship between the user identifier and the user information stored in the user database corresponding to the operator is obtained.
  • the user information corresponding to the user identifier can improve the efficiency of obtaining user information.
  • the user state of the user is a suspended state, and the user state of the user may change from a normal state to a suspended state because the user owes a fee.
  • the management platform receives the authentication and charging request message, where the authentication and charging request message carries the user identifier IDB and the identifier sms of the capability interface to be invoked, and obtains the correspondence between the user identifier and the user information according to the user identifier IDB. Corresponding user information is verified according to the user status included in the user information. If the user status included in the user information is normal, the verification is passed, and the user identification range in which the user identification is located is determined, and the user identifier is further obtained. The operator corresponding to the user ID range, and the ID of the operator is IDC.
  • Step 305 The management platform obtains a correspondence from the identifier of the stored capability interface, the identifier of the operator, and the product price information according to the identifier of the capability interface to be invoked and the identifier of the operator to which the user corresponding to the user identifier belongs.
  • Product price information, the product price information includes at least product price, currency unit and billing strategy;
  • the management platform is based on the identifier of the capability interface to be invoked and the identifier IDC of the operator to which the user corresponding to the user identifier IDB belongs, from the identifier of the stored capability interface, the identifier of the operator, and the product price information.
  • Obtaining corresponding product price information the product price information includes a product price, a currency unit, and a charging policy, and the paying party information defined by the charging policy is information such as a user.
  • Step 306 The management platform obtains the charging object and the charging fee according to the obtained product price and the charging policy, and sends a deduction request message to the charging system corresponding to the operator to which the corresponding user belongs, the deduction request The message carries the identifier, charging fee and currency unit of the obtained charging object;
  • the management platform determines the charging object according to the charging party information included in the obtained charging policy, calculates the charging fee according to the obtained product price and the charging policy, and sends a deduction request message to the user corresponding to the user identifier.
  • the billing system corresponding to the operator, the deduction request message carries the identifier of the determined billing object, the obtained billing fee, and the currency unit.
  • the determined charging object is the user corresponding to the user identifier, and the identifier of the charging object is the user identifier, if the obtained charging policy includes the payment If the party information is a third party, the determined charging object is a third party corresponding to the identifier of the third party, and the identifier of the charging object is the identifier of the third party.
  • the billing system receives the billing request message, where the billing request message carries the identifier of the billing object, the billing fee, and the currency unit, and the billing object corresponding to the identifier of the billing object is pre-paid with the operator. If the method is prepaid, the charging object corresponding to the identifier of the charging object is prepaid according to the charging fee and the currency unit. If the prepaid payment is successful, the charging response message is sent to the management platform, and the deduction response message is sent.
  • the charging response message is sent to the management platform, and the debit response message carries the identification information of the charging failure; if the charging object corresponding to the charging object identifier is in advance
  • the bill is generated, and the deduction response message is sent to the management platform, and the deduction response message carries the identification information of the successful billing.
  • the management platform determines, according to the paying party information included in the obtained charging policy, that the charging object is the user corresponding to the user identifier IDB, calculates the charging fee according to the obtained product price and the charging policy, and sends a deduction fee.
  • the request message is sent to the charging system corresponding to the operator to which the user corresponding to the IDB belongs, and the debit request message carries the identifier IDB of the determined charging object, the obtained charging fee and the currency unit;
  • the payment method of the operator signing is prepaid, and the charging system receives the deduction request message, and prepays the charging object corresponding to the IDB of the charging object according to the charging fee and the currency unit, and the prepaid is successful.
  • the deduction response message is sent, and the deduction response message carries the identification information of the charging success.
  • the charging policy includes at least the paying party information and the charging rule, and the management platform calculates the charging fee according to the product price and the charging rule in the charging policy.
  • the management platform may also be based on the product price and the charging policy.
  • the charging fee is calculated by one or more kinds of information other than the charging rule included in the charging rule and the charging policy.
  • the price of the product is one for each message, and the operator to which the user corresponding to the user ID is associated with the user has 100 free SMS messages per month
  • the charging rule includes information such as the number of free short messages of 100, and the management platform. First, it is judged whether the number of free short messages used by the user in the current month reaches 100. If yes, the charging fee is calculated as 1 cent according to the product price, and if not, the obtained charging fee is 0.
  • Step 307 The management platform receives the chargeback response message sent by the charging system. If the chargeback response message carries the identifier information of the successful charging, the authentication and charging response message is sent to the access gateway, and the authentication and charging response message is sent. Carrying the identifier of the operator to which the user corresponding to the user identifier belongs;
  • Step 308 The access gateway receives the authentication and charging response message, and invokes the corresponding according to the identifier of the capability interface to be invoked.
  • the capability interface, and the information to be sent is sent to the capability component corresponding to the operator to which the user corresponding to the user identifier belongs by using the invoked capability interface;
  • the capability component corresponding to the operator to which the user identifier corresponds is sent to the corresponding user according to the user identifier included in the information to be sent, and the reply is sent after the sending is completed.
  • the response message is sent to the access gateway.
  • the capability component of the operator is the short message center.
  • the access gateway calls the corresponding Sms interface according to the identifier sms of the capability interface to be called, and sends the short message to be sent to the user identifier IDB through the Sms interface.
  • the SMS center of the operator to which the user belongs the short message center sends a short message to be sent to the corresponding user according to the user ID of the to-be-sent message, and sends a response message to the access gateway.
  • Step 309 The access gateway receives the response message sent by the capability component, and sends an authentication and charging confirmation request message to the management platform.
  • Step 310 After receiving the authentication and charging request message, the management platform sends a deduction confirmation request message to the charging system corresponding to the operator to which the user corresponding to the user identifier belongs;
  • the charging system performs the deduction confirmation operation after receiving the deduction confirmation request message, and then sends a deduction confirmation response message to the management platform.
  • Step 311 The management platform receives the charging system to send a deduction confirmation response message, and sends an authentication and charging confirmation response message to the access gateway.
  • the management platform receives the authentication and charging request message sent by the access gateway, where the authentication and charging request message carries the identifier of the third party, the user identifier, and the identifier of the capability interface to be invoked, according to the stored
  • the identifier of the capability interface the correspondence between the identifier of the operator and the product price information, the identifier of the third party, the identifier of the user, and the identifier of the capability interface to be invoked, obtain the operator and charging information of the user corresponding to the user identifier
  • the fee information includes at least the identifier of the billing object, the billing fee, and the currency unit, and the billing request message is sent to the billing system of the operator to which the user corresponding to the user identifier belongs, and the billing request message carries the billing information.
  • the charging system is caused to perform charging according to the charging information.
  • the SDP can support multiple operators, multiple operators share one SDP, reduce the cost of the carrier, and when the third party uses the capabilities of multiple operators, only need to call a capability interface corresponding to the capability on the SDP. , reduce the cost of using third parties.
  • a charging management device including:
  • the receiving module 401 is configured to receive an authentication charging request message sent by the access gateway, where the authentication charging request message carries the user identifier and an identifier of the capability interface to be invoked;
  • the obtaining module 402 is configured to obtain, according to the identifier of the stored capability interface, the identifier of the operator, and the product price information, the operator and the charging information to which the user corresponding to the user identifier belongs;
  • the sending module 403 is configured to send a charging request message to the charging system of the operator to which the corresponding user belongs, and the charging request message carries the obtained charging information, so that the charging system performs the charging information according to the charging information. Billing.
  • the charging information includes at least the identifier of the charging object, the charging fee, and the currency unit.
  • the obtaining module 402 includes: a determining unit, configured to determine, according to the user identifier, an identifier of an operator to which the user corresponding to the user identifier belongs; An obtaining unit, configured to obtain corresponding product price information from the identifier of the stored capability interface, the identifier of the operator, and the product price information according to the identifier of the capability interface to be invoked and the identifier of the acquired operator,
  • the product price information includes at least a product price, a currency unit, and a charging policy, and the charging policy includes at least payer information and charging rules;
  • a second obtaining unit configured to obtain an identifier of the charging object according to the paying party information included in the charging policy, and calculate a charging fee according to the product price and the charging policy.
  • the determining unit is configured to determine a range of user identifiers to which the user identifier belongs, and obtain an operator corresponding to the user identifier range, where the obtained operator is an operator to which the user corresponding to the user identifier belongs.
  • the second obtaining unit includes:
  • a first determining subunit configured to: if the charging party information included in the charging policy is a user, determine that the identifier of the charging object is the user identifier;
  • a second determining subunit configured to: if the charging party information included in the charging policy is a third party, determine that the identifier of the charging object is an identifier of the third party;
  • a calculation subunit configured to calculate a charging fee according to the product price and the charging policy.
  • the device further includes:
  • a verification module configured to obtain, according to the user identifier, the corresponding user information from the stored relationship between the user identifier and the user information, where the user information includes at least a user status, where the user status includes a normal status or a suspended status, according to the user information.
  • the user status of the user identifier is verified by the user status, and if the verification is passed, the operation of acquiring the operator and the charging information of the user corresponding to the user identifier is performed.
  • the device further includes:
  • a storage module configured to receive a user information synchronization request message sent by an operator's information system, where the user information synchronization request message carries a user identifier and user information of a user to which the operator belongs, the user information includes at least a user status, and the user is stored.
  • the user ID and user information of the user carried in the information synchronization request message.
  • the authentication charging request message sent by the access gateway is received, and the authentication charging request message carries The identifier of the user interface and the capability interface to be invoked, and the carrier and the charging information of the user corresponding to the user identifier are obtained according to the identifier of the stored capability interface, the identifier of the operator, and the product price information.
  • the billing information includes at least the identifier of the billing object, the billing fee, and the currency unit, and the billing request message is sent to the billing system of the operator to which the user corresponding to the user identifier belongs, and the billing request message carries the billing information. And causing the charging system to perform charging according to the charging information.
  • the SDP can support multiple operators, multiple operators share one SDP, reduce the cost of the carrier, and when the third party uses the capabilities of multiple operators, only need to call a capability interface corresponding to the capability on the SDP. , reduce the cost of using third parties.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention, qui se rapporte au domaine des communications, concerne un procédé et dispositif de gestion de facturation. Le procédé consiste à : recevoir une demande d'authentification et de facturation envoyée par une passerelle d'accès, la demande d'authentification et de facturation contenant une identité d'un abonné et une identité d'une interface de capacité à appeler ; acquérir des informations d'opérateur et de facturation au sujet d'un abonné correspondant à l'identité de l'abonné selon des correspondances stockées entre l'identité de l'interface de capacité, l'identité d'un opérateur et des informations de prix de produit ; et envoyer un message de soustraction de frais au système de facturation de l'opérateur de l'abonné correspondant à l'identité de l'abonné, le message de demande de soustraction de frais contenant les informations de facturation pour permettre au système de facturation d'effectuer un prélèvement selon les informations de facturation. Le dispositif comprend un module de réception, un module d'acquisition et un module d'émission. La présente invention peut diminuer les coûts de l'opérateur et les coûts d'utilisation de tierce partie.
PCT/CN2012/077617 2012-06-27 2012-06-27 Procédé et dispositif de gestion de facturation WO2014000179A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2012/077617 WO2014000179A1 (fr) 2012-06-27 2012-06-27 Procédé et dispositif de gestion de facturation
CN201280000552.1A CN103650416A (zh) 2012-06-27 2012-06-27 一种计费管理方法及设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/077617 WO2014000179A1 (fr) 2012-06-27 2012-06-27 Procédé et dispositif de gestion de facturation

Publications (1)

Publication Number Publication Date
WO2014000179A1 true WO2014000179A1 (fr) 2014-01-03

Family

ID=49782045

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/077617 WO2014000179A1 (fr) 2012-06-27 2012-06-27 Procédé et dispositif de gestion de facturation

Country Status (2)

Country Link
CN (1) CN103650416A (fr)
WO (1) WO2014000179A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111274248A (zh) * 2020-01-19 2020-06-12 北京金堤科技有限公司 一种计费数据的生成方法及装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111309758B (zh) * 2020-01-19 2024-02-13 北京金堤科技有限公司 一种计费数据验证比对方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859135A (zh) * 2006-03-13 2006-11-08 华为技术有限公司 一种wap业务计费方法
CN101023623A (zh) * 2004-05-12 2007-08-22 托吉瓦控股股份公司 在ip网络中基于内容进行计费的方法和系统
CN101064616A (zh) * 2006-04-28 2007-10-31 华为技术有限公司 一种网络计费方法、系统及设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009572B (zh) * 2006-01-24 2012-07-04 朗迅科技公司 对于ims会话期间的媒体改变的ims预算控制
CN101378586B (zh) * 2007-08-27 2012-08-29 华为技术有限公司 一种业务数据流的策略控制方法、装置及系统
CN101409627B (zh) * 2007-10-09 2011-02-02 华为技术有限公司 跨网络关联计费的方法、网络设备、计费实体和计费系统
CN101420675B (zh) * 2007-10-22 2010-11-10 华为技术有限公司 计费方法及会话控制信令面锚点

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101023623A (zh) * 2004-05-12 2007-08-22 托吉瓦控股股份公司 在ip网络中基于内容进行计费的方法和系统
CN1859135A (zh) * 2006-03-13 2006-11-08 华为技术有限公司 一种wap业务计费方法
CN101064616A (zh) * 2006-04-28 2007-10-31 华为技术有限公司 一种网络计费方法、系统及设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111274248A (zh) * 2020-01-19 2020-06-12 北京金堤科技有限公司 一种计费数据的生成方法及装置

Also Published As

Publication number Publication date
CN103650416A (zh) 2014-03-19

Similar Documents

Publication Publication Date Title
JP4940298B2 (ja) 後払い情報通信システムにおける前払いセキュリティ機構
US8260254B2 (en) Network billing
US7729485B2 (en) Telecommunications network having number portability
US20070297583A1 (en) Method and System for Third Party Charging
WO2006111095A1 (fr) Reseau de charge, appareil formant agent de charge et procede de charge correspondant
WO2013139230A1 (fr) Procédé et système de charge de communication de type machine (mtc), et entité de traitement de message
KR20150073189A (ko) 인스턴트 메시징 시스템 및 방법
WO2010063176A1 (fr) Procédé de facturation d'appel fondé sur un système de facturation en ligne et système de communication
CN101860838B (zh) 一种预付费计费方法及系统
CN103379462B (zh) 一种用于处理计费请求的方法和装置
RU2005118984A (ru) Способ организации предоплаченной услуги обмена мультимедийными сообщениями
WO2007048348A1 (fr) Procede et systeme de realisation de facturation des services de publicite
KR100509936B1 (ko) 이동통신망에서 멀티미디어 데이터의 선불형 지능망서비스 제공 시스템 및 방법
WO2012100524A1 (fr) Système et procédé pour contrôler des arriérés de service
WO2014000179A1 (fr) Procédé et dispositif de gestion de facturation
WO2012062076A1 (fr) Procédé et système de facturation de service de prépaiement pour un réseau privé virtuel intégré (ivpn)
WO2006066508A1 (fr) Procede et systeme de commande d'appel, systeme facilitant l'exploitation commerciale et point de commande de services
CN103136881B (zh) 支付方法和支付系统
WO2014177098A1 (fr) Procédé et système de traitement de paiement en ligne à l'aide d'un logiciel d'application
KR20060002122A (ko) 잔액 소진 상태의 선불 요금 가입자를 위한 무선 데이터서비스 방법 및 시스템
WO2017000644A1 (fr) Procédé et dispositif permettant un partage de ressources de compte
US9241250B2 (en) System and method to support mediation of OCS diameter/RO reauthorization on GSM camel networks
WO2010069184A1 (fr) Procédé et système pour effectuer la facturation dans un service de réponse vocale inactive (ivr)
WO2016177233A1 (fr) Procédé et dispositif de facturation flexible
KR101452413B1 (ko) 패킷 한도 만료 시 데이터 서비스 제공 시스템 및 방법

Legal Events

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

Ref document number: 12880176

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12880176

Country of ref document: EP

Kind code of ref document: A1