WO2007014533A1 - Procede permettant d'acceder au systeme de taxation par une application de service, moteur de taxation et reseau de taxation associe - Google Patents

Procede permettant d'acceder au systeme de taxation par une application de service, moteur de taxation et reseau de taxation associe Download PDF

Info

Publication number
WO2007014533A1
WO2007014533A1 PCT/CN2006/001947 CN2006001947W WO2007014533A1 WO 2007014533 A1 WO2007014533 A1 WO 2007014533A1 CN 2006001947 W CN2006001947 W CN 2006001947W WO 2007014533 A1 WO2007014533 A1 WO 2007014533A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
user
event
engine
service
Prior art date
Application number
PCT/CN2006/001947
Other languages
English (en)
Chinese (zh)
Inventor
Mingjun Shan
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 WO2007014533A1 publication Critical patent/WO2007014533A1/fr

Links

Classifications

    • 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

Definitions

  • the present invention relates to the field of wireless packet service charging technologies, and in particular, to a method for opening an mobile alliance service application access charging system, and a method Billing engine and a billing network.
  • OMA Open Mobile Alliance
  • the Open Mobile Alliance (OMA) an international non-profit organization, is dedicated to the development and promotion of standards for wireless business applications. Its mission is to find a system-independent, open standard that enables applications and services to be interconnected across a wide range of terminals worldwide. Promote growth in the entire mobile industry market by enabling customers to use interoperable mobile services between different markets, carriers, and mobile terminals. This is achieved by defining a framework based on open standards. The framework allows for the secure, efficient creation, configuration, and management of applications and services in a multi-vendor environment.
  • the business areas currently being developed by OMA include browsing-type services, communication services, entertainment services, and e-commerce.
  • both the type of services and the number of services have been rapidly developed, and in systems such as CDAM2000, WCDMA, TD-SCDMA or WLAN, the bandwidth of the packet domain is sufficient to support more users to experience better services. Appearance.
  • terminals have become more and more complex, and the growth of terminal holding rate has also promoted the growth of a wide range of wireless services based on wireless networks.
  • Typical wireless services include: mobile payment services, multimedia messaging, instant messaging, PTT and Mobile games, etc.
  • the charging network of the OMA service mainly includes multiple service application servers and multiple charging systems.
  • the service application server may be a multimedia message center (MMSC), a cellular-based push-to-talk server (POC Server), a Presence server, a location server, Game server, instant messaging server (IM Server) or personal information management server (PIM Server).
  • the billing system includes an online billing system and an offline billing system, wherein the online billing system may be an intelligent network billing system of an operator domain or a credit card payment system of an internet domain, and the offline billing system may be an operation support system (OSS). ), billing support system (BSS), etc.
  • OSS operation support system
  • BSS billing support system
  • the service server and the charging system in the same carrier are usually provided by different vendors, and the service forms, service requirements, and charging requirements of the respective service applications are different.
  • the requirements for billing, billing, billing by time, etc. are also different, so the service server and the billing system or billing agent implement billing through a proprietary billing interface.
  • the communication protocols between the business components and the billing system are also often different.
  • FIG. 1 shows a charging network that implements charging for three types of services.
  • the multimedia message service after the MMSC 101 performs an MMS service, the MMSC initiates a charging request according to the charging, and the charging interface 1 charges the charging.
  • the request is converted into a protocol format supported by the charging system 110, and sent to the charging system 110.
  • the charging system 110 deducts the fee according to the charging request, and the charging protocol of the charging interface 1 is HTTP protocol.
  • the POC server 102 After the POC Server 102 performs a service, the POC server initiates a charging request for the flow rate, and the charging interface 2 converts the charging request into a protocol supported by the charging system 110. The form is sent to the charging system 110.
  • the charging system 110 After receiving the charging request, the charging system 110 deducts the fee according to the charging request, and the charging protocol of the charging interface 2 is SOAP. Similarly, for the VOD service, the VOD service server 103 initiates a charging request based on the duration charging after performing the primary service, and the charging interface 3 converts the charging request into a protocol supported by the charging system 110 to send the charging. The system 110 then charges the user for the charging system.
  • the charging protocol of the charging interface 3 is TCP/IP.
  • a proprietary charging interface is used between the service application server and the charging system in the prior art, and the proprietary charging interface has a very high degree of coupling with the service, that is, each charging connection.
  • the ports are respectively adapted to different protocols according to different service server adaptation protocols, and each charging interface can implement only one charging mode. Therefore, the charging interface in the prior art has low reusability, and when a new service is launched, a new service development cycle is added because the charging mode and the charging interface are separately opened for the new service.
  • each charging system since each charging system usually implements charging with a plurality of service application servers through a proprietary charging interface, the complexity of the charging system is very high, which is not conducive to the maintenance of the charging system.
  • a first object of the present invention is to provide a method for an OMA service application access charging system, which can implement charging requirements of various OMA services, so that each service application can be conveniently accessed.
  • the billing network implements billing.
  • a second object of the present invention is to provide a billing engine that can be applied to different business applications and billing facilities.
  • a third object of the present invention is to provide a charging network capable of realizing the charging requirements of various services, so that each service application can conveniently access the charging network to implement charging.
  • the present invention provides a method for accessing a charging system by a service application, the method comprising:
  • the charging client sends a charging event including a user identifier and an event type to the charging engine;
  • the charging engine After the charging engine receives the charging event from the charging client, if it is an offline charging user, the charging event is sent to the corresponding offline charging system for the user to deduct the fee, such as If the online charging user performs step C;
  • the corresponding online charging system determines, according to the event type in the charging event, whether the charging attribute of the service is billed according to the item, and if yes, sending the charging request according to the item to the corresponding online charging system after performing the service pricing , the user is charged; otherwise, if it is determined that the service charging attribute is the session charging according to the mode of time length, flow rate, etc., the corresponding online charging system is initiated with a withholding, and is used for the current withholding amount. After that, the user is again deducted from the corresponding online charging system to deduct the fee for the user, and after the business is completed, the unused credit is returned to the user account.
  • the billing and withholding units include, but are not limited to: amount, duration, virtual item, data flow, and the like.
  • the method may further include: performing credit control on the user in the charging event.
  • the method further includes: performing authentication and authentication on the user in the charging event.
  • the method further includes: performing credit control and authentication authentication on the user in the charging event, or performing authentication authentication and credit authentication.
  • the method can be applied to, but not limited to, the following network standards: CDAM2000, WCDMA, TD-SCDMA or WLAN.
  • the present invention provides a charging engine, which includes: a charging interface module and a bearer protocol adaptation module, respectively, on the charging client side and the charging facility side;
  • the charging interface module on the charging client side of the charging engine is configured to determine a user attribute according to the user identifier in the charging event sent by the charging client, and if the user attribute is an offline charging user, The charging protocol submitted to the charging client side is suitable for the charging protocol. If the user attribute is an online charging user, the corresponding charging mode is determined according to the event type in the charging event, and an accounting request or a withholding request message is generated, and then the generated charging request or the withholding request is generated. 'met's submitted to the bearer protocol adaptation module on the billing client side;
  • the bearer protocol adaptation module of the charging client side of the charging engine is configured to convert information from the charging interface module of the charging client side into a pre-set general protocol and send the bearer protocol to the charging facility side. Adapting the module, and converting the information from the charging protocol adaptation module on the charging facility side to the charging interface module that is identifiable by the charging client to the charging client side;
  • the bearer protocol adaptation module on the charging facility side of the charging engine is configured to convert information from the charging client side bearer protocol adaptation module into information that the charging facility side can recognize and send to the charging.
  • a charging interface module on the facility side and converting the information from the charging interface module on the charging facility side into a general protocol to the bearer protocol adaptation module on the charging client side;
  • the charging interface module on the charging facility side of the charging engine is configured to charge the user for interaction with the corresponding charging facility according to the received charging event, charging request, or withholding request.
  • the general protocol may be: HTTP protocol, TCP/IP protocol, SOAP protocol, OMA CH-1 interface protocol, OMA CH-2 interface protocol, 3GPP Ro interface protocol or 3GPP Rf interface protocol.
  • the charging engine is applied to, but not limited to, the following network standards: CDAM2000, WCDMA, TD-SCDMA, or WLAN.
  • the present invention provides a charging network, which includes a charging client, a charging engine, an online charging system, and an offline charging system; Used to send a charging event including a user identifier and an event type to the charging engine;
  • the charging engine is configured to receive a charging event from the charging client, and if the user is an offline charging user, send the charging event to the corresponding offline charging system, and if it is an online charging user, according to the charging event.
  • the event type in the service determines whether the service charging attribute is charged according to the bar, and if so, sends a chargeback request to the corresponding online charging system to charge the user; if the service is determined to be charged
  • the attribute is session charging, and the pre-deduction request is sent to the corresponding online charging system;
  • the offline charging system is configured to perform deduction according to a charging request from a charging engine; the online charging system is configured to perform deduction according to a deduction request and a withholding request from a charging engine.
  • the charging engine determines the user attribute according to the user identifier in the charging event, and determines the corresponding according to the user attribute and the charging event type.
  • the charging request that can be identified by the charging facility side is sent to the charging facility to charge the user, thereby realizing the charging requirement for multiple OMA services, so that each service application can conveniently access the charging network. Realize billing;
  • the present invention provides a charging interface module capable of implementing multiple charging modes in a charging engine, and converts the information into a general protocol through a bearer protocol adaptation module, so that the charging engine can be applied to different accounting
  • the billing between the client and the billing facility is implemented, and the billing facility is connected to the plurality of service service components through a billing interface and a bearer protocol adaptation conversion module, thereby reducing the complexity of the billing system and reducing the complexity.
  • the difficulty of maintaining the billing system In addition, when the service is newly built, the service application server does not need to develop the billing mode, and the billing system does not need to be upgraded. Only the universal billing engine needs to be applied to realize billing between the two. , reducing the development cycle of new business.
  • FIG. 1 is a composition diagram of a prior art charging network according to the present invention.
  • FIG. 2 is a composition diagram of a charging network in a specific embodiment of the present invention.
  • FIG. 3 is a network composition diagram of a specific application of the present invention.
  • the main idea of the present invention is to provide a method for accessing a charging system of an OMA service application.
  • each service application can conveniently access the charging system.
  • Its own complex billing such as charging according to the flow rate, billing by time, billing by content, billing by bar, etc., supports various payment methods.
  • the present invention can be applied to communication systems such as WCDMA, CDMA2000, TD-SCDMA or WLAN.
  • the charging network is composed as shown in FIG. 2, and includes a charging client part (Charging Client) and a charging facility part (Charging Infrastructure).
  • the Charging Client includes a Service Application Server (App) 210, a Service Application Server Agent (App Agent) 211, a Charging Interface Module (Charging I/F) 220, and a Bearer Protocol Adaptation Module (Adapter) 230.
  • the Charging Infrastructure includes an adapter adapter module (Adapter) 231, a Charging Interface Module (Charging I/F) 221, and a billing system 240.
  • Business application server and business application server The proxy acts as a billing client.
  • the service application server may also directly connect to the charging interface module without using the service application server proxy.
  • the charging system may also be a charging proxy.
  • the charging interface module (Charging I/F) 220, and the bearer protocol adaptation module (Adapter) 230, the bearer protocol adaptation module (Adapter) 231, and the charging interface module (Charging I/F) 221 constitute a billing engine 200.
  • the service application server and the service application server agent are OMA service applications, that is, the billing client; the billing system and the billing agent are billing facilities.
  • the App210 and the App Agent 211 are core processing parts of the service, and send a charging event to the Charging I/F 220 after the service is in progress or after the service is completed.
  • the charging event includes a user identifier, an event type, such as a download service, and an MMS service. Etc., and initiator information, receiver information, and so on.
  • the Charging I/F 220 determines the user attribute according to the user identifier in the charging event, such as whether the user is an online charging user or an offline charging user, and whether the user sets the consumption. The quota, whether authentication authentication is required, etc. If it is determined that the user sets the consumption limit, that is, it is determined that the user needs to perform credit control, the user in the event is authenticated by credit, and if authentication is required, the user in the event is authenticated. Perform authentication authentication, and determine whether the user is an online charging user or an offline charging user after the authentication is passed; otherwise, directly determine whether the user is an online charging user or an offline charging user.
  • the received charging event is submitted to the Adapter 230; if it is determined that the user is an online charging user, according to the user type Determine the corresponding charging method with the preset charging method in Charging I/F220, and generate a standard debit request or withholding request after the service is denominated according to the determined charging method, and generate the deduction request. Or a withholding request is submitted to the Adapter230.
  • the charging method mentioned here may include: billing by bar, billing by content, billing by time, billing by flow, or a combination of these.
  • the charging request is generated, that is, the charging request, where the charging request includes the number of events or the number of the items, such as sending
  • the generated billing request may include virtual items; Generate a withholding request. If the charging method is based on the long-term charging, the generated withholding request includes the online time, such as the online time of the POC service, and the online time of the PRECENSE service; if the charging method is based on the flow rate, the generated withholding request includes : The actual number of byte streams, such as the number of bytes that occur in a streaming-based service.
  • the Charging I/F 220 determines that the original withholding amount of the user has been exhausted before receiving the information of the end of the service, and then generates a withholding request again, through the Adapter 230 and The Adapter231 is sent to the corresponding Charging I/F221 for pre-deduction.
  • the Charging I/F 220 calculates the accumulated consumption amount of the service, calculates the unconsumed credit amount, and then includes the information of the unconsumed credit of the current service. It is sent back to the user account via the Adapter230 and Adapter231 to the corresponding Charging I/F221.
  • the Adapter 230 After receiving the information from the Charging I/F 220, the Adapter 230 converts the received information into a preset general protocol, and then sends the information to the corresponding offline charging system or the Adapter of the online charging system, that is, the corresponding charging facility side.
  • the general protocol referred to herein may be the HTTP protocol, the TCP/IP protocol, the SOAP protocol, the OMA CH-1 interface protocol, the OMA CH-2 interface protocol, the 3GPP Ro interface protocol, or the 3GPP Rf interface protocol.
  • the Adapter 231 on the charging facility side After receiving the information from the Adapter 230, the Adapter 231 on the charging facility side converts the information into information that can be identified by the corresponding offline charging system or the corresponding online charging system, and sends the information to the corresponding offline charging system. Or corresponding online charging system Charging I/F22L
  • the Charging I/F 221 After receiving the information from the Adapter231, the Charging I/F 221 exchanges with the corresponding charging facility to charge the user.
  • FIG. 3 is a network component structure diagram of a specific application of the present invention, where each billing The Charging I/F and Adapter on the facility side can interact with Adapter and Charging I/F on multiple service application server sides to implement billing for multiple business application servers. Similarly, in this embodiment, the Charging I/F and Adapter on each service application server side can also interact with the Adapter and Charging I/F on multiple charging facility sides.
  • the process of this embodiment includes the following steps:
  • Step 401 After the service is in progress or after the service is completed, the service application server sends a charging event to the charging engine, where the charging event includes a user identifier, an event type, an initiator information, and a receiving end information, and the event type may be Such as downloading business, MMS business, etc.
  • Step 402 After receiving the charging event from the service application server, the charging engine determines whether the user sets the consumption limit. If yes, step 403 is performed; otherwise, step 404 is performed.
  • Step 403 Determine that the user sets a consumption limit, that is, after determining that the user needs to perform credit authentication, the charging engine performs credit authentication for the user in the charging event and the corresponding system interaction, and determines the user credit authentication. Whether it is passed, if it is step 404; otherwise, step 411 is performed.
  • the system referred to in this step may be a billing system or other system for storing user credit information.
  • Step 404 The charging engine determines whether the user needs to perform authentication authentication. If yes, execute step 405; otherwise, perform step 406.
  • Step 405 The charging engine performs authentication authentication for the user in the charging event and the corresponding system interaction, and determines whether the user authentication authentication is passed. If yes, go to step 406; otherwise, perform step 412.
  • the system described in this step is a system for storing user authentication information, which may be an HLR or the like.
  • Step 406 determining whether the user is an offline charging user, if yes, executing step 407; Otherwise, step 408 is performed.
  • Step 407 Convert the received charging event into information that can be identified by the corresponding offline charging system, and then send the information to the corresponding offline charging system, where the offline charging system charges the user according to the received charging event.
  • Step 408 The charging engine determines a corresponding charging mode according to the charging event and multiple charging modes preset in the charging mode, and generates a corresponding online charging system to be identified after performing service pricing according to the charging mode. Deduction request or withholding request, and then converting the generated deduction request or withholding request into information that can be identified by the corresponding online charging system, and then sending the information to the corresponding online charging system for the user to deduct; and receiving After the pre-trip response information returned by the online charging system, the pre-catch response information is converted into information that can be recognized by the service application server, and then sent to the corresponding service application server.
  • the charging method in this step may include: billing by bar, billing by content, billing by time, billing by flow, or a combination of these. If the charging mode is the charging according to the bar, the charging request is generated, where the charging request includes the number of events or the number of the number of the MMS, such as the number of the MMS to be sent, the number of times the ringtone is downloaded, and the like; The fee may include a virtual item in the generated charging request; if the charging method is the session charging according to the duration or the flow rate, a withholding request is generated.
  • the generated withholding request includes the online time, such as the online time of the POC service, and the online time of the PRECENSE service; if the charging method is based on the flow rate, the generated withholding request includes : The actual number of byte streams, such as the number of bytes that occur in a streaming-based service.
  • the accounting engine determines that the amount of the user's withholding has been consumed, the pre-deduction request is generated again, and after converting the information to the corresponding online charging system, the information is sent to the corresponding online.
  • the billing system performs a withholding.
  • Step 409 After receiving the withholding response information, the service application server continues to perform the service, and sends a message to the charging engine to notify the end of the service after the service is completed.
  • Step 410 After receiving the information about the end of the service, the billing engine calculates the cumulative consumption amount of the service, and calculates the unconsumed credit amount, and then converts the rollback request including the unconsumed credit of the current service into a corresponding one. The information that the online charging system can recognize is sent to the corresponding online charging system, and the online charging system returns the unpaid credit to the user's account.
  • Step 411 The charging engine returns a credit authentication failure message to the service application server, and notifies the user that the credit authentication fails.
  • Step 412 The charging engine returns an authentication authentication failure message to the service application server, and notifies that the user authentication fails.
  • the service application server in the above process may also be a service application server proxy, and the billing system may also be a billing proxy.

Landscapes

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

Abstract

L'invention concerne un procédé permettant d'accéder au système de taxation par une application de service OMA. Ce procédé accueille la taxation de divers services d'application OMA, y compris la taxation en fonction du flux, du temps, du contenu ou de la fréquence. Ce procédé remplis différentes conditions et la fonction principale de traitement logique de taxation comprend les fonctions de contrôle du crédit, de déduction de frais, de taxation des services, de pré-déduction et de pré-déduction à différentes reprises, d'annulation de la pré-déduction, etc. L'invention concerne également un moteur de taxation (200) et un réseau de taxation. Le moteur de taxation (200) génère la demande de taxation qui peut être identifiée par l'infrastructure de taxation et l'envoie à l'infrastructure de taxation afin de compléter la déduction de frais conformément au type de taxation correspondant déterminé par l'attribut d'utilisateur déterminé par l'identificateur d'utilisateur dans l'événement de taxation et le type d'événement de taxation après avoir reçu l'événement de taxation du serveur d'application de service (210), de façon que la présente invention puisse remplir la condition de taxation pour de multiples services OMA. Par ailleurs, le moteur de taxation rend chaque service accessible via le réseau de taxation afin d'effectuer une taxation avantageuse.
PCT/CN2006/001947 2005-08-03 2006-08-02 Procede permettant d'acceder au systeme de taxation par une application de service, moteur de taxation et reseau de taxation associe WO2007014533A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 200510089025 CN1794638A (zh) 2005-08-03 2005-08-03 Oma业务应用接入计费系统的方法和计费引擎
CN200510089025.4 2005-08-03

Publications (1)

Publication Number Publication Date
WO2007014533A1 true WO2007014533A1 (fr) 2007-02-08

Family

ID=36805930

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001947 WO2007014533A1 (fr) 2005-08-03 2006-08-02 Procede permettant d'acceder au systeme de taxation par une application de service, moteur de taxation et reseau de taxation associe

Country Status (2)

Country Link
CN (1) CN1794638A (fr)
WO (1) WO2007014533A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102595365A (zh) * 2012-03-08 2012-07-18 北京神州数码思特奇信息技术股份有限公司 一种业务组件式开发方法
CN113222676A (zh) * 2021-06-03 2021-08-06 上海中通吉网络技术有限公司 高动态扩展性引擎计费方法

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132289B (zh) * 2006-08-24 2011-04-13 华为技术有限公司 融合计费方法及计费系统及应用服务器及融合计费系统
CN101350727B (zh) * 2007-07-18 2010-10-20 华为技术有限公司 帐户数据快照方法、装置、帐务平衡方法及实时计费系统
CN101374044B (zh) * 2007-08-21 2010-12-15 中国电信股份有限公司 一种使业务引擎获得用户标识的方法和系统
CN101453721B (zh) * 2007-12-05 2010-12-08 华为技术有限公司 Ims网络中非sip应用的计费方法、系统及计费事件上报单元
CN101188505B (zh) * 2007-12-11 2011-12-07 华为技术有限公司 内容类型识别的方法和设备
CN102164358B (zh) * 2010-02-24 2014-03-05 华为技术有限公司 业务处理的方法和装置
CN102209310B (zh) * 2010-03-31 2014-06-25 华为技术有限公司 对用户业务的数据流进行控制的方法和装置
CN102104861A (zh) * 2011-02-15 2011-06-22 中兴通讯股份有限公司 一种业务处理方法及系统
CN109787783A (zh) * 2019-03-27 2019-05-21 山东浪潮云信息技术有限公司 一种公有云环境下的计费实现系统及方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1412972A (zh) * 2001-10-04 2003-04-23 阿尔卡塔尔公司 支持服务收费的控制服务器
EP1437693A1 (fr) * 2003-01-08 2004-07-14 Itsmobile Limited Système et méthode de télécommunication mobile pour le routage de facturation
CN1645805A (zh) * 2004-04-01 2005-07-27 华为技术有限公司 一种分组数据业务的计费控制方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1412972A (zh) * 2001-10-04 2003-04-23 阿尔卡塔尔公司 支持服务收费的控制服务器
EP1437693A1 (fr) * 2003-01-08 2004-07-14 Itsmobile Limited Système et méthode de télécommunication mobile pour le routage de facturation
CN1645805A (zh) * 2004-04-01 2005-07-27 华为技术有限公司 一种分组数据业务的计费控制方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102595365A (zh) * 2012-03-08 2012-07-18 北京神州数码思特奇信息技术股份有限公司 一种业务组件式开发方法
CN113222676A (zh) * 2021-06-03 2021-08-06 上海中通吉网络技术有限公司 高动态扩展性引擎计费方法

Also Published As

Publication number Publication date
CN1794638A (zh) 2006-06-28

Similar Documents

Publication Publication Date Title
WO2007014533A1 (fr) Procede permettant d'acceder au systeme de taxation par une application de service, moteur de taxation et reseau de taxation associe
JP4842317B2 (ja) オンライン課金管理サーバー
US8548427B2 (en) System and method for peer-to-peer transfer of multimedia content and reconciliation thereof
CN1757025B (zh) 利用显式服务授权为网络服务提供预付费计费的方法和装置
EP1802028B2 (fr) Reseau de charge, appareil formant agent de charge et procede de charge correspondant
US7885636B2 (en) Data pre-paid in simple IP data roaming
CN101227302B (zh) 计费方法、控制装置、计费装置与计费系统
JP5417438B2 (ja) ショートメッセージ配信に対する課金
WO2004036871A1 (fr) Gestion de l'information de facturation dans une structure d'interfonctionnement entre un reseau de communication mobile et un reseau local
CN103460642A (zh) 用于控制通信网络中的服务业务的方法和设备
JP2006186986A (ja) Ｉｍｓネットワークでオンラインの課金をするためのｉｍｓゲートウェイ・システムおよび方法
WO2007082446A1 (fr) Procede et systeme de taxation hors ligne
US20090144167A1 (en) System and method for managing data and voice connectivity for wireless devices
US20140101040A1 (en) Method and apparatus for charging in a communication network
CN101026664B (zh) 一种预付费业务计费方法及系统
CN107800545A (zh) 一种基于边缘计算的话单计算系统及方法
WO2007048348A1 (fr) Procede et systeme de realisation de facturation des services de publicite
WO2009059503A1 (fr) Procédé de traitement de reddition de comptes, système de réseau, système de reddition de compte et serveur commercial
WO2007137482A1 (fr) Procédé, système et dispositif de taxation dans un réseau d'interfonctionnement du système hyperfréquence global
KR100588625B1 (ko) 잔액 소진 상태의 선불 요금 가입자를 위한 무선 데이터서비스 방법 및 시스템
KR100621203B1 (ko) 선불 및 한도 가입자를 위한 무선 데이터 서비스 제어방법 및 시스템
WO2008148355A1 (fr) Procédé, système et appareil de facturation
CN101447878B (zh) 一种预付费业务的计费方法与系统
CN1848900A (zh) 一种预付费的计费方法
WO2012089000A1 (fr) Procédé, passerelle et système de communication pour facturer un utilisateur de paiement différé

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06775273

Country of ref document: EP

Kind code of ref document: A1