WO2011150688A1 - Charging method and system for prepaid service - Google Patents

Charging method and system for prepaid service Download PDF

Info

Publication number
WO2011150688A1
WO2011150688A1 PCT/CN2011/070071 CN2011070071W WO2011150688A1 WO 2011150688 A1 WO2011150688 A1 WO 2011150688A1 CN 2011070071 W CN2011070071 W CN 2011070071W WO 2011150688 A1 WO2011150688 A1 WO 2011150688A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
service
management platform
service management
module
Prior art date
Application number
PCT/CN2011/070071
Other languages
French (fr)
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 中兴通讯股份有限公司
Publication of WO2011150688A1 publication Critical patent/WO2011150688A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1467—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving prepayment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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
    • 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/59—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on real time
    • 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/83—Notification aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/855—Successful event
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/856—Unsuccessful event
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity

Definitions

  • the present invention relates to the field of communications, and in particular to a method and system for charging a prepaid service.
  • BACKGROUND With the continuous development of telecom value-added services, people have put forward higher requirements for the diversification and stability of value-added service products, and the accuracy of charging for prepaid systems is even more so.
  • the service management platform In the existing value-added service system, for prepaid users, the service management platform needs to send a message to the prepaid system for deduction in real time, but due to many factors such as network anomaly, the link between the prepaid system and the service management platform may appear. Abnormalities such as broken links, signaling return timeouts, etc.
  • a primary object of the present invention is to provide a prepaid service charging method and system to solve the above problems.
  • a charging service charging method including: a service management platform monitors a link state between a service management platform and a prepaid system in real time; and receives a service engine from a service management platform.
  • a prepaid service charging system including: a service management platform and a prepaid system, wherein the service management platform includes: an abnormality monitoring module, a cache module, and a notification module.
  • the abnormality monitoring module is configured to monitor the link status between the service management platform and the prepaid system in real time. If the service management platform receives the charging request message from the service engine, the link status is abnormal. Status, the cache module is triggered; the cache module is used for caching corresponding to the charging request cancellation Billing information, and trigger the notification module.
  • the notification module is configured to send a charging success message to the service engine.
  • the prepaid system includes: an acquisition module and a supplementary charging module.
  • the obtaining module is configured to obtain charging information from the cache module, and the supplementary charging module is configured to perform supplementary charging according to the charging information acquired by the obtaining module.
  • the link between the service management platform and the prepaid system is dynamically monitored. When the link is abnormal, the service management platform saves the charging information and notifies the service when the link is abnormal. The engine billing was successful.
  • the technical solution of the present invention in the process of charging the prepaid subscribers, even if the link between the service management platform and the prepaid system is abnormal, the user can ensure the normal use of the service and ensure the accuracy of the charging.
  • FIG. 1 is a flowchart of a prepaid charging application scenario according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a prepaid charging method according to an embodiment of the present invention
  • FIG. 3 is a second embodiment of the present invention.
  • FIG. 4 is a flow chart of the charging in the normal case of the link in the third embodiment of the present invention;
  • FIG. 5 is a flowchart in the case of a link abnormality according to the fourth embodiment of the present invention
  • FIG. 6 is a structural block diagram of a prepaid service charging system according to Embodiment 5 of the present invention.
  • BEST MODE FOR CARRYING OUT THE INVENTION the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • FIG. 1 is a schematic diagram of a prepaid charging application scenario according to an embodiment of the present invention. As shown in FIG. 1, the prepaid charging service involves the following network elements: a user, a service provider SP, a service engine, a service management platform, and a prepaid system. .
  • the foregoing network element implements charging of the prepaid user in the following manner: the service provider SP sends a message to the service engine; the service engine sends the authentication deduction message to the service management platform, and the service management platform sends a real-time deduction.
  • the fee message is sent to the prepaid system, and the prepaid system completes the charging in time; the prepaid system returns the deduction fee successfully; the service management platform returns the authentication success response to the service I engine; the service engine sends a message to the user.
  • Embodiment 1 a prepaid service charging method is provided.
  • FIG. 2 is a flowchart of a prepaid service charging method according to the first embodiment of the present invention. The process includes: Step S202: The service management platform is in real time.
  • Step S204 When the service management platform receives the charging request message from the service engine, and monitors that the link status is abnormal, the cache corresponds to charging. The charging information of the request message is requested, and the charging success message is sent to the service engine.
  • the service management platform receives the charging request message from the service engine, and monitors that the link status is abnormal, the cache corresponds to charging. The charging information of the request message is requested, and the charging success message is sent to the service engine.
  • the service management platform may, but is not limited to, sending monitoring signaling to the prepaid system, monitoring the link status, setting the monitoring response time, and exceeding the threshold number when the response signaling is not received within the predetermined response time. After that, you can determine that the link is abnormal.
  • the actual service related signaling exchanged between the service management platform and the prepaid system can also be monitored to monitor the link status, and the monitoring mode is similar to the proprietary monitoring signaling.
  • the service management platform when receiving the charging request message from the service engine (accounting request for a specific service of a specific user), the service management platform determines the current link status according to the monitoring result of the real-time monitoring; Normally, the existing real-time prepaid charging method is used for charging, that is, the real-time charging message is sent to the pre-paid system, and the pre-paid system responds to the message, and deducts the cost of the service from the account of the specific user. And returning the response message to notify the service management system that the charging is successful, and the service management system forwards the charging success message to the service engine; if the link is abnormal, temporarily records the charging information corresponding to the charging request message, so as to ensure that the link is abnormal.
  • the service that affects the normal use of the user is sent to the service engine, so that the service engine can deliver the downlink data provided by the SP to the user.
  • the method provided in this embodiment may further include: recording the charging information in an offline file preset by the service management platform.
  • the service management platform locally configures an offline file for the link abnormality to be used for storing the charging information of all users requesting the service service when the link is abnormal.
  • the method further includes: the service management platform knowing that the user has successfully used the service corresponding to the charging request message.
  • the service management platform sends the charging success message, although the service engine is notified that the user is successfully charged, in reality, the prepaid system has not completed charging for the user.
  • the service management platform It is also necessary to determine whether the service engine delivers the downlink data provided by the SP to the user, that is, whether the user has used the requested service normally, and if so, the cached charging information is recorded in the offline file; otherwise, the charging information is discarded.
  • the above-mentioned preferred way of recording offline files is such that the service management platform does not record the previously cached charging information when it knows that the user is not using the service normally, because the user does not obtain the service service, and therefore should not generate a fee. Therefore, the billing error is avoided, and the operator's monthly service quality and the legitimate rights and interests of the user are guaranteed.
  • the service management platform knows that the user has successfully used the service corresponding to the charging request message by:
  • the service management platform receives a charging confirmation message from the service engine
  • the service management platform parses from the charging confirmation message to the indication information indicating that the user has successfully used the service.
  • the method may further include: the prepaid system acquiring the offline file, and performing supplementary charging according to the charging information recorded in the offline file.
  • the prepaid system can be triggered to obtain an offline file by using the following method: In the process of monitoring the link in real time, the service management platform notifies the prepaid system to the abnormal link. Obtain offline files for supplementary billing. Manner 2: Set the acquisition period, and the prepaid system actively obtains offline files for supplementary charging from the service management platform every predetermined period.
  • the prepaid system realizes subsequent supplementary charging, so that the charging is accurate, and the interests of the operator and the SP supplier are guaranteed.
  • the service management platform selects the real-time charging mode to notify the prepaid system of charging, and after that, the service management platform learns that the user that has been billed has not used the service request normally.
  • the prepaid billing system should notify the prepaid system to refund the user's fee. If the service management platform monitors the link between the service management platform and the prepaid system abnormally during the refund process, The existing real-time refund method cannot refund the deducted fees.
  • This embodiment provides a better prepaid service charging method. In addition to the technical features described in the first embodiment, the above problem can be solved. FIG.
  • Step S302 When the service management platform receives the charging confirmation message from the service engine, the service management platform monitors that the link status is abnormal.
  • step S304 the service management platform resolves from the charging confirmation message to indicate that the user is unsuccessful.
  • the indication information of the service corresponding to the charging confirmation message is used;
  • Step S306 buffers the refund information corresponding to the charging confirmation message, and sends a refund success message to the service engine.
  • the method further includes: recording the refund information in an offline file of the service management platform.
  • the method further includes: the prepaid system acquiring the offline file, and performing the supplementary refund according to the refund information recorded by the offline file.
  • the abnormality of the link between the service management platform and the prepaid system does not affect the user's refund operation, thereby ensuring not only the normal operation of the service but also the economic loss of the user.
  • FIG. 4 is a flow chart of charging under normal link conditions according to Embodiment 3 of the present invention.
  • the process includes: Step S401: The SP sends a message to the service engine.
  • Step S402 The service engine sends an authentication deduction request to the service management platform.
  • Step S403 The service management platform determines that the current link status is normal, and then directly sends a real-time deduction.
  • the service message engine sends a message to the user.
  • step S405 the service management platform returns a successful authentication response to the service engine.
  • Step S406 The service engine sends a message to the user.
  • Embodiment 4 The embodiment provides a charging process in the case of a link abnormality between the service management platform and the prepaid system.
  • FIG. 5 is a charging process in the case of a link abnormality according to the fourth embodiment of the present invention.
  • the processing flow is as follows: In step S501, the SP sends a message to the service engine.
  • Step S502 The service engine sends an authentication deduction request to the service management platform.
  • Step S503 The service management platform determines that the current link status is abnormal, and returns a deduction success message to the service engine. And the service charge engine sends a message to the user;
  • Step S504 the service engine sends an authentication deduction confirmation message to the service management platform, to identify whether the user has successfully used the service;
  • Step S506 the service management platform gives the service The engine returns a response message for confirming the deduction of the deduction; in step S507, the service management platform processes the data according to whether the user has successfully used the service: if the user has successfully used the service, the offline file recording module is called, and the deduction information is written into the offline. File, and identified as a chargeback timeout.
  • FIG. 6 is a structural block diagram of a prepaid service charging system according to Embodiment 5 of the present invention.
  • the system includes: a service management platform 60 and a prepaid system. 62.
  • the service management platform 60 includes: an abnormality monitoring module 600, a cache module 602, and a notification module 604.
  • the abnormality monitoring module 600 is configured to monitor a link state between the service management platform 60 and the prepaid system 62 in real time.
  • the prepaid system 62 includes: an obtaining module 620 and a supplementary charging module 622, wherein the obtaining module 620 is configured to obtain charging information from the cache module 602, and the supplementary charging module 622 is configured to perform charging according to the obtaining module 620. Information is supplemented for billing.
  • the abnormality monitoring module 600 monitors that the link status is abnormal, and triggers the cache module 602 to buffer the refund information; the cache module 602 is further used.
  • the charging module corresponding to the charging confirmation message is cached, and the notification module 604 is triggered.
  • the notification module 604 is further configured to send a refund success message to the service engine.
  • the obtaining module 620 of the prepaid system 62 is further used for The refunding information is obtained from the cache module 602.
  • the prepaid system 62 may further include: a supplementary refunding module 624, configured to perform a supplementary refund according to the refund information acquired by the obtaining module 620.
  • the supplementary refunding module 624 and the supplementary charging module 622 may be separately set or may be set in one.
  • the technical solution provided by the embodiment of the invention can implement the charging and refunding work in the case that the link of the prepaid system is normal and abnormal, and does not affect the normal use of the service by the user. It not only improves the user experience, but also improves the quality of the business, and ensures the legitimate rights and interests of users, operators and SPs.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
  • the computing device may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A charging method and system for prepaid service are disclosed by the present invention. In the above-mentioned method, a service management platform monitors the state of the link between the service management platform and a prepaid system in real time; when receiving a charging request message from a service engine, if the service management platform detects that the link is in an abnormal state, the service management platform cashes the charging information corresponding to the charging request message and transmits a charging success message to the service engine. In the course of charging a prepaid user, even though the link between the service management platform and the prepaid system becomes abnormal, the technical solutions of the present invention can ensure that the user uses services normally, and ensure the charging accuracy, thus the prepaid charging system with high user experience is enabled.

Description

预付费业务计费方法和*** 技术领域 本发明涉及通信领域，具体而言， 涉及一种预付费业务计费方法和***。 背景技术 随着电信增值业务的不断发展， 人们对增值业务产品的多样化及稳定性 都提出了更高要求， 对预付费***计费的准确性更是如此。 在现有增值业务 ***中， 针对预付费用户， 业务管理平台需要实时发消息到预付费***进行 扣费， 但是由于网络异常等诸多因素， 预付费***与业务管理平台之间的链 路可能出现断链、 信令返回超时等异常。 发明人发现， 当预付费***与业务管理平台之间的链路出现异常时， 由 于扣费失败， 业务管理平台会向业务引擎返回鉴权失败消息， 业务引擎收到 鉴权失败消息后则不会向用户下发 SP提供的下行消息， 从而造成用户在这 种情况下无法使用业务。 发明内容 本发明的主要目的在于提供一种预付费业务计费方法和***， 以解决上 述问题。 根据本发明的一个方面， 提供了一种付费业务计费方法， 包括： 业务管 理平台实时地监控业务管理平台与预付费***之间的链路状态； 在业务管理 平台接收到来自于业务引擎的计费请求消息时，监控到链路状态为异常状态， 则緩存对应于计费请求消息的计费信息， 并向业务引擎发送计费成功消息。 根据本发明的另一方面， 提供了一种预付费业务计费***， 包括： 业务 管理平台和预付费***， 其中， 业务管理平台包括： 异常监控模块、 緩存模块以及通知模块。 其中， 异 常监控模块， 用于实时地监控业务管理平台与预付费***之间的链路状态， 如果在业务管理平台接收到来自于业务引擎的计费请求消息时， 监控到链路 状态为异常状态， 则触发緩存模块； 緩存模块， 用于緩存对应于计费请求消 息的计费信息， 并触发通知模块。 通知模块， 用于向业务引擎发送计费成功 消息。 预付费***包括： 获取模块、 补充计费模块。 其中， 获取模块， 用于从 緩存模块中获取计费信息； 补充计费模块， 用于根据获取模块获取的计费信 息进行补充计费。 通过本发明， 釆用对业务管理平台与预付费***之间的链路进行动态监 控， 当监控到链路异常时， 业务管理平台在监控到链路异常时， 保存计费信 息， 并通知业务引擎计费成功。 通过本发明的技术方案， 在对预付费用户计 费的过程中， 即使业务管理平台与预付费***之间的链路出现异常， 也可以 保证用户正常使用业务， 并且保证计费的准确性， 从而使得预付费计费*** 有很高的用户体验。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中： 图 1是根据本发明实施例的预付费计费应用场景图； 图 2是根据本发明实施例一的预付费业务计费方法流程图； 图 3是 居本发明实施例二的链路异常情况下的退费流程图； 图 4是 居本发明实施例三的链路正常情况下的计费流程图； 图 5是根据本发明实施例四的链路异常情况下的计费流程； 图 6是 居本发明实施例五的预付费业务计费***结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互组合。 图 1是 居本发明实施例的预付费计费应用场景图， 如图 1所示， 预付 费计费服务涉及到以下网元： 用户、 服务商 SP、 业务引擎、 业务管理平台以 及预付费***。 上述网元在计费应用过程中， 以如下方式实现预付费用户的计费： 服务 商 SP下发消息到业务引擎； 业务引擎发鉴权扣费消息到业务管理平台， 业 务管理平台发实时扣费消息到预付费***， 由预付费***及时完成计费； 预 付费***返回扣费成功响应； 业务管理平台返回鉴权成功响应给业务 I擎； 业务引擎下发消息到用户。 实施例一 在本实施例中， 提供一种预付费业务计费方法， 图 2是根据本发明实施 例一的预付费业务计费方法流程图， 该流程包括： 步骤 S202,业务管理平台实时地监控业务管理平台与预付费***之间的 链路状态； 步骤 S204, 在业务管理平台接收到来自于业务引擎的计费请求消息时， 监控到链路状态为异常状态， 则緩存对应于计费请求消息的计费信息， 并向 业务引擎发送计费成功消息。 相关技术中， 在对预付费用户计费的过程中， 由于缺少链路异常情况的 处理机制， 使得一旦预付费***与业务管理平台之间的链路出现异常， 由于 无法完成计费， 从而造成用户在这种情况下无法使用业务。 本实施例提供的 上述方法， 提出链路异常情况的处理机制， 即使业务管理平台与预付费*** 之间的链路出现异常， 也可以保证用户正常使用业务， 并且保证计费的准确 性， 从而使得预付费计费***有很高的用户体验。 在实施过程中， 业务管理平台可以但不限于通过向预付费***发送监控 信令， 监控链路状态， 设定监控响应时间， 当在预定响应时间内没有接收到 响应信令的情况超过门限次数后， 即可确定链路出现异常。 为减少业务管理 平台和预付费***的处理负荷， 也可以监控业务管理平台和预付费***之间 交互的与实际业务相关的信令来监控链路状态， 监控方式与专有监控信令类 似。 在实施过程中， 业务管理平台在接收到来自于业务引擎的计费请求消息 (针对特定用户的特定业务的计费请求） 时， 根据实时监控的监控结果， 判 断当前链路状态； 如果链路正常， 则釆用现有的实时预付费计费方式进行计费， 即向预付 费***发送实时计费消息， 预付费***响应该消息， 从该特定用户的账户中 扣除此次业务的费用， 并返回响应消息通知业务管理***计费成功， 业务管 理***向业务引擎转发计费成功消息； 如果链路异常， 则暂且记录与上述计费请求消息对应的计费信息， 为保 证链路异常不会影响到用户正常使用请求的业务， 先发送计费成功消息给业 务引擎， 这样， 业务引擎即可向用户下发 SP提供的下行数据。 优选地， 在发送计费成功消息之后， 本实施例提供的方法还可以包括： 将计费信息记录在业务管理平台预先设置的离线文件中。 在实施过程中， 业务管理平台预先在本地配置针对发生链路异常情况的 离线文件， 用于存储在链路发生异常时， 所有请求业务服务的用户的计费信 息。 通过以上优选的记录计费信息的方式， 可以将发生链路异常情况下的所 有用户的计费信息组织在一起， 便于预付费***之后统一地进行补充计费。 优选地， 在将计费信息记录在业务管理平台的离线文件之前， 还包括： 业务管理平台获知用户已经成功使用计费请求消息对应的业务。 在实施过程中， 业务管理平台在发送计费成功消息之后， 虽然通知了业 务引擎该用户计费成功，但实际上，预付费***还没有完成对该用户的计费， 此时， 业务管理平台还需要判断业务引擎是否向用户下发 SP提供的下行数 据， 即用户是否已经正常使用了请求的业务， 如果是， 才将緩存的计费信息 记录在离线文件中， 否则， 丢弃该计费信息。 通过上述优选的记录离线文件的方式， 使得业务管理平台在获知用户未 正常使用业务的情况下， 不记录之前緩存的计费信息， 因为此种情况用户并 没有获得业务服务， 因此不应该产生费用， 从而避免了计费错误， 保证了运 营商的月艮务质量和用户的合法权益。 优选地， 业务管理平台通过以下方式获知用户已经成功使用计费请求消 息对应的业务： The present invention relates to the field of communications, and in particular to a method and system for charging a prepaid service. BACKGROUND With the continuous development of telecom value-added services, people have put forward higher requirements for the diversification and stability of value-added service products, and the accuracy of charging for prepaid systems is even more so. In the existing value-added service system, for prepaid users, the service management platform needs to send a message to the prepaid system for deduction in real time, but due to many factors such as network anomaly, the link between the prepaid system and the service management platform may appear. Abnormalities such as broken links, signaling return timeouts, etc. The inventor finds that when the link between the prepaid system and the service management platform is abnormal, the service management platform returns an authentication failure message to the service engine because the deduction fails, and the service engine does not receive the authentication failure message. The downlink message provided by the SP is sent to the user, so that the user cannot use the service in this case. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a prepaid service charging method and system to solve the above problems. According to an aspect of the present invention, a charging service charging method is provided, including: a service management platform monitors a link state between a service management platform and a prepaid system in real time; and receives a service engine from a service management platform. When the charging request message is sent, the link status is monitored as an abnormal state, and the charging information corresponding to the charging request message is buffered, and the charging success message is sent to the service engine. According to another aspect of the present invention, a prepaid service charging system is provided, including: a service management platform and a prepaid system, wherein the service management platform includes: an abnormality monitoring module, a cache module, and a notification module. The abnormality monitoring module is configured to monitor the link status between the service management platform and the prepaid system in real time. If the service management platform receives the charging request message from the service engine, the link status is abnormal. Status, the cache module is triggered; the cache module is used for caching corresponding to the charging request cancellation Billing information, and trigger the notification module. The notification module is configured to send a charging success message to the service engine. The prepaid system includes: an acquisition module and a supplementary charging module. The obtaining module is configured to obtain charging information from the cache module, and the supplementary charging module is configured to perform supplementary charging according to the charging information acquired by the obtaining module. With the present invention, the link between the service management platform and the prepaid system is dynamically monitored. When the link is abnormal, the service management platform saves the charging information and notifies the service when the link is abnormal. The engine billing was successful. With the technical solution of the present invention, in the process of charging the prepaid subscribers, even if the link between the service management platform and the prepaid system is abnormal, the user can ensure the normal use of the service and ensure the accuracy of the charging. This allows the prepaid billing system to have a high user experience. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a flowchart of a prepaid charging application scenario according to an embodiment of the present invention; FIG. 2 is a flowchart of a prepaid charging method according to an embodiment of the present invention; FIG. 3 is a second embodiment of the present invention. FIG. 4 is a flow chart of the charging in the normal case of the link in the third embodiment of the present invention; FIG. 5 is a flowchart in the case of a link abnormality according to the fourth embodiment of the present invention; FIG. 6 is a structural block diagram of a prepaid service charging system according to Embodiment 5 of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. FIG. 1 is a schematic diagram of a prepaid charging application scenario according to an embodiment of the present invention. As shown in FIG. 1, the prepaid charging service involves the following network elements: a user, a service provider SP, a service engine, a service management platform, and a prepaid system. . In the charging application process, the foregoing network element implements charging of the prepaid user in the following manner: the service provider SP sends a message to the service engine; the service engine sends the authentication deduction message to the service management platform, and the service management platform sends a real-time deduction. The fee message is sent to the prepaid system, and the prepaid system completes the charging in time; the prepaid system returns the deduction fee successfully; the service management platform returns the authentication success response to the service I engine; the service engine sends a message to the user. Embodiment 1 In this embodiment, a prepaid service charging method is provided. FIG. 2 is a flowchart of a prepaid service charging method according to the first embodiment of the present invention. The process includes: Step S202: The service management platform is in real time. Monitoring the link status between the service management platform and the prepaid system; Step S204: When the service management platform receives the charging request message from the service engine, and monitors that the link status is abnormal, the cache corresponds to charging. The charging information of the request message is requested, and the charging success message is sent to the service engine. In the related art, in the process of charging a prepaid subscriber, due to the lack of a link abnormality processing mechanism, once the link between the prepaid system and the service management platform is abnormal, the billing cannot be completed, thereby causing Users cannot use the business in this situation. The foregoing method provided by the embodiment provides a processing mechanism for the abnormality of the link. Even if the link between the service management platform and the prepaid system is abnormal, the user can ensure the normal use of the service and ensure the accuracy of the charging. The prepaid billing system has a high user experience. In the implementation process, the service management platform may, but is not limited to, sending monitoring signaling to the prepaid system, monitoring the link status, setting the monitoring response time, and exceeding the threshold number when the response signaling is not received within the predetermined response time. After that, you can determine that the link is abnormal. In order to reduce the processing load of the service management platform and the prepaid system, the actual service related signaling exchanged between the service management platform and the prepaid system can also be monitored to monitor the link status, and the monitoring mode is similar to the proprietary monitoring signaling. In the implementation process, when receiving the charging request message from the service engine (accounting request for a specific service of a specific user), the service management platform determines the current link status according to the monitoring result of the real-time monitoring; Normally, the existing real-time prepaid charging method is used for charging, that is, the real-time charging message is sent to the pre-paid system, and the pre-paid system responds to the message, and deducts the cost of the service from the account of the specific user. And returning the response message to notify the service management system that the charging is successful, and the service management system forwards the charging success message to the service engine; if the link is abnormal, temporarily records the charging information corresponding to the charging request message, so as to ensure that the link is abnormal. The service that affects the normal use of the user is sent to the service engine, so that the service engine can deliver the downlink data provided by the SP to the user. Preferably, after the sending the charging success message, the method provided in this embodiment may further include: recording the charging information in an offline file preset by the service management platform. During the implementation process, the service management platform locally configures an offline file for the link abnormality to be used for storing the charging information of all users requesting the service service when the link is abnormal. Through the above preferred method of recording the charging information, the charging information of all users in the case of a link abnormality can be organized together, so that the prepaid system can uniformly perform supplementary charging afterwards. Preferably, before the accounting information is recorded in the offline file of the service management platform, the method further includes: the service management platform knowing that the user has successfully used the service corresponding to the charging request message. In the implementation process, after the service management platform sends the charging success message, although the service engine is notified that the user is successfully charged, in reality, the prepaid system has not completed charging for the user. At this time, the service management platform It is also necessary to determine whether the service engine delivers the downlink data provided by the SP to the user, that is, whether the user has used the requested service normally, and if so, the cached charging information is recorded in the offline file; otherwise, the charging information is discarded. . The above-mentioned preferred way of recording offline files is such that the service management platform does not record the previously cached charging information when it knows that the user is not using the service normally, because the user does not obtain the service service, and therefore should not generate a fee. Therefore, the billing error is avoided, and the operator's monthly service quality and the legitimate rights and interests of the user are guaranteed. Preferably, the service management platform knows that the user has successfully used the service corresponding to the charging request message by:
( 1 ) 业务管理平台接收来自于业务引擎的计费确认消息； (1) The service management platform receives a charging confirmation message from the service engine;
( 2 ) 业务管理平台从计费确认消息中解析到指示用户已经成功使用业 务的指示信息。 优选地， 在将计费信息记录在业务管理平台的离线文件之后， 上述方法 还可以包括： 预付费***获取离线文件， 并根据离线文件中记录的计费信息 进行补充计费。 在具体实施过程中， 可以但不限于通过以下方式触发预付费***获取离 线文件： 方式一、 业务管理平台实时监控链路的过程中， 一旦发现异常的链路恢 复正常， 则通知预付费***到本地获取离线文件进行补充计费。 方式二、 设定获取周期， 预付费***每隔预定周期， 均主动向业务管理 平台获取离线文件进行补充计费。 通过上述优选的方法， 预付费***实现了后续的补充计费， 使得计费准 确， 保证了运营商和 SP供应商的利益。 实施例二 在实际应用中， 还存在这样一种情况： 即业务管理平台选择实时计费方 式通知预付费***计费， 在此之后， 业务管理平台获知已经计费过的用户没 有正常使用业务请求， 此时， 预付费计费***应该通知预付费***退还该用 户的费用， 如果在进行退费的过程中， 业务管理平台监控到业务管理平台与 预付费***之间的链路出现异常， 则现有的实时退费方法无法退还已扣掉的 费用。 本实施例提供一种更优的预付费业务计费方法， 除具有上述实施例一描 述的技术特征之外， 还可以解决上述问题。 图 3是 居本发明实施例二的链路异常情况下的退费流程图， 该流程包 括： 步骤 S302, 在业务管理平台接收到来自于业务引擎的计费确认消息时, 业务管理平台监控到链路状态为异常状态； 步骤 S304,业务管理平台从计费确认消息中解析到指示用户未成功使用 对应于计费确认消息的业务的指示信息； 步骤 S306緩存对应于计费确认消息的退费信息， 并向业务引擎发送退 费成功消息。 优选地， 在发送退费成功消息之后， 还包括： 将退费信息记录在业务管 理平台的离线文件中。 优选地,在将退费信息记录在业务管理平台的离线文件中之后，还包括： 预付费***获取离线文件， 并根据离线文件记录的退费信息进行补充退费。 通过上述优选的计费方法， 使得业务管理平台与预付费***之间的链路 的异常， 不会影响到用户的退费操作， 从而不仅保证了业务的正常进行， 而 且避免了用户的经济损失。 实施例三 本实施例提供一种业务管理平台与预付费***间的链路正常情况下的计 费处理流程， 图 4是根据本发明实施例三的链路正常情况下的计费流程图， 该流程包括： 步骤 S401 , SP下发消息到业务引擎； 步骤 S402, 业务引擎发鉴权扣费请求到业务管理平台； 步骤 S403 , 业务管理平台判断出当前链路状态正常， 于是直接发实时扣 费消息到预付费***； 步 4聚 S404 , 预付费***返回扣费成功响应； 步骤 S405 , 业务管理平台返回鉴权计费成功响应给业务引擎； 步骤 S406, 业务引擎下发消息到用户。 实施例四 本实施例提供一种业务管理平台与预付费***间的链路异常情况下的计 费处理方法， 图 5是根据本发明实施例四的链路异常情况下的计费流程， 处 理流程如下： 步骤 S501 , SP下发消息到业务引擎； 步骤 S502 , 业务引擎发鉴权扣费请求到业务管理平台； 步骤 S503 , 业务管理平台判断出当前链路状态异常， 返回扣费成功消息 给业务引擎， 并记录扣费信息； 步骤 S504 , 业务引擎下发消息到用户； 步骤 S505 , 业务引擎发送鉴权扣费确认消息给业务管理平台， 标识用户 是否已成功使用业务； 步骤 S506 , 业务管理平台给业务引擎返回鉴权扣费确认的响应消息； 步骤 S507 , 业务管理平台才艮据用户是否已成功使用业务作出处理： 如果 用户已成功使用业务， 则调用离线文件记录模块，将扣费信息写进离线文件， 并标识为扣费超时。 如果用户没有成功使用业务， 则不记录离线文件； 步骤 S508 , 预付费***定期从业务管理平台取离线文件进行处理， 发现 其标识为超时， 则对用户进行补扣费， 完成扣费过程。 实施例五 在本实施例中， 提供一种预付费业务计费***， 图 6是根据本发明实施 例五的预付费业务计费***结构框图， 该***包括： 业务管理平台 60和预 付费*** 62 , 其中， 业务管理平台 60包括： 异常监控模块 600、 緩存模块 602以及通知模块 604 , 其中， 异常监控模块 600 , 用于实时地监控业务管理平台 60与预付费 *** 62之间的链路状态， 如果在业务管理平台 60接收到来自于业务引擎的 计费请求消息时， 监控到链路状态为异常状态， 则触发緩存模块 602 ; 緩存 模块 602 , 用于緩存对应于计费请求消息的计费信息， 并触发通知模块 604; 通知模块 604 , 用于向业务引擎发送计费成功消息。 预付费*** 62包括： 获取模块 620以及补充计费模块 622 , 其中， 获取 模块 620 , 用于从緩存模块 602中获取计费信息； 补充计费模块 622 , 用于 根据获取模块 620获取的计费信息进行补充计费。 优选地， 在业务管理平台 60接收到来自于业务引擎的计费确认消息时， 异常监控模块 600监控到链路状态为异常状态， 则触发緩存模块 602緩存退 费信息； 緩存模块 602 , 还用于緩存对应于计费确认消息的退费信息， 并触 发通知模块 604; 通知模块 604 , 还用于向业务引擎发送退费成功消息； 优选地， 预付费*** 62的获取模块 620 , 还用于从緩存模块 602中获取 退费信息； 预付费*** 62还可以包括： 补充退费模块 624 , 用于才艮据获取模 块 620获取的退费信息进行补充退费。 需要说明的是， 在实施过程中， 补充退费模块 624和补充计费模块 622 可以分开设置， 也可以合一设置。 本发明实施例提供的技术方案， 在预付费***的链路正常和异常的情况 下都能实现计费和退费工作， 不影响用户正常使用业务。 不仅提高了用户体 验度， 提高了业务的月艮务质量， 而且确保了用户、 运营商以及 SP月艮务商的 合法权益。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 并 且在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步骤， 或者 将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软件 结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的^"神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。 (2) The service management platform parses from the charging confirmation message to the indication information indicating that the user has successfully used the service. Preferably, after the charging information is recorded in the offline file of the service management platform, the method may further include: the prepaid system acquiring the offline file, and performing supplementary charging according to the charging information recorded in the offline file. In a specific implementation process, the prepaid system can be triggered to obtain an offline file by using the following method: In the process of monitoring the link in real time, the service management platform notifies the prepaid system to the abnormal link. Obtain offline files for supplementary billing. Manner 2: Set the acquisition period, and the prepaid system actively obtains offline files for supplementary charging from the service management platform every predetermined period. Through the above preferred method, the prepaid system realizes subsequent supplementary charging, so that the charging is accurate, and the interests of the operator and the SP supplier are guaranteed. In the second embodiment, in a practical application, the service management platform selects the real-time charging mode to notify the prepaid system of charging, and after that, the service management platform learns that the user that has been billed has not used the service request normally. At this time, the prepaid billing system should notify the prepaid system to refund the user's fee. If the service management platform monitors the link between the service management platform and the prepaid system abnormally during the refund process, The existing real-time refund method cannot refund the deducted fees. This embodiment provides a better prepaid service charging method. In addition to the technical features described in the first embodiment, the above problem can be solved. FIG. 3 is a flowchart of a refund in the case of a link abnormality according to the second embodiment of the present invention, where the process includes: Step S302: When the service management platform receives the charging confirmation message from the service engine, the service management platform monitors that the link status is abnormal. In step S304, the service management platform resolves from the charging confirmation message to indicate that the user is unsuccessful. The indication information of the service corresponding to the charging confirmation message is used; Step S306 buffers the refund information corresponding to the charging confirmation message, and sends a refund success message to the service engine. Preferably, after the sending the refund success message, the method further includes: recording the refund information in an offline file of the service management platform. Preferably, after the refund information is recorded in the offline file of the service management platform, the method further includes: the prepaid system acquiring the offline file, and performing the supplementary refund according to the refund information recorded by the offline file. Through the above preferred charging method, the abnormality of the link between the service management platform and the prepaid system does not affect the user's refund operation, thereby ensuring not only the normal operation of the service but also the economic loss of the user. . Embodiment 3 This embodiment provides a charging process flow when a link between a service management platform and a prepaid system is normal, and FIG. 4 is a flow chart of charging under normal link conditions according to Embodiment 3 of the present invention. The process includes: Step S401: The SP sends a message to the service engine. Step S402: The service engine sends an authentication deduction request to the service management platform. Step S403: The service management platform determines that the current link status is normal, and then directly sends a real-time deduction. The service message engine sends a message to the user. In step S405, the service management platform returns a successful authentication response to the service engine. Step S406: The service engine sends a message to the user. Embodiment 4 The embodiment provides a charging process in the case of a link abnormality between the service management platform and the prepaid system. FIG. 5 is a charging process in the case of a link abnormality according to the fourth embodiment of the present invention. The processing flow is as follows: In step S501, the SP sends a message to the service engine. Step S502: The service engine sends an authentication deduction request to the service management platform. Step S503: The service management platform determines that the current link status is abnormal, and returns a deduction success message to the service engine. And the service charge engine sends a message to the user; Step S504, the service engine sends an authentication deduction confirmation message to the service management platform, to identify whether the user has successfully used the service; Step S506, the service management platform gives the service The engine returns a response message for confirming the deduction of the deduction; in step S507, the service management platform processes the data according to whether the user has successfully used the service: if the user has successfully used the service, the offline file recording module is called, and the deduction information is written into the offline. File, and identified as a chargeback timeout. If the user does not successfully use the service, the offline file is not recorded; Step S508, the prepaid system periodically takes the offline file from the service management platform for processing, and finds that the identifier is timeout, then the user is charged and the deduction process is completed. Embodiment 5 In this embodiment, a prepaid service charging system is provided. FIG. 6 is a structural block diagram of a prepaid service charging system according to Embodiment 5 of the present invention. The system includes: a service management platform 60 and a prepaid system. 62. The service management platform 60 includes: an abnormality monitoring module 600, a cache module 602, and a notification module 604. The abnormality monitoring module 600 is configured to monitor a link state between the service management platform 60 and the prepaid system 62 in real time. If the service management platform 60 receives the charging request message from the service engine, and monitors that the link status is abnormal, the buffering module 602 is triggered; the cache module 602 is configured to cache the accounting corresponding to the charging request message. The fee information, and trigger notification module 604; the notification module 604 is configured to send a charging success message to the service engine. The prepaid system 62 includes: an obtaining module 620 and a supplementary charging module 622, wherein the obtaining module 620 is configured to obtain charging information from the cache module 602, and the supplementary charging module 622 is configured to perform charging according to the obtaining module 620. Information is supplemented for billing. Preferably, when the service management platform 60 receives the charging confirmation message from the service engine, the abnormality monitoring module 600 monitors that the link status is abnormal, and triggers the cache module 602 to buffer the refund information; the cache module 602 is further used. The charging module corresponding to the charging confirmation message is cached, and the notification module 604 is triggered. The notification module 604 is further configured to send a refund success message to the service engine. Preferably, the obtaining module 620 of the prepaid system 62 is further used for The refunding information is obtained from the cache module 602. The prepaid system 62 may further include: a supplementary refunding module 624, configured to perform a supplementary refund according to the refund information acquired by the obtaining module 620. It should be noted that, during the implementation process, the supplementary refunding module 624 and the supplementary charging module 622 may be separately set or may be set in one. The technical solution provided by the embodiment of the invention can implement the charging and refunding work in the case that the link of the prepaid system is normal and abnormal, and does not affect the normal use of the service by the user. It not only improves the user experience, but also improves the quality of the business, and ensures the legitimate rights and interests of users, operators and SPs. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

权 利 要 求 书 Claim
1. 一种预付费业务计费方法， 其特征在于， 包括： A method for charging a prepaid service, comprising:
业务管理平台实时地监控业务管理平台与预付费***之间的链路 状态；  The service management platform monitors the link status between the service management platform and the prepaid system in real time;
在所述业务管理平台接收到来自于业务引擎的计费请求消息时， 监控到所述链路状态为异常状态， 则緩存对应于所述计费请求消息的 计费信息， 并向所述业务引擎发送计费成功消息。  When the service management platform receives the charging request message from the service engine, if the link status is abnormal, the charging information corresponding to the charging request message is buffered, and the service is The engine sends a billing success message.
2. 根据权利要求 1所述的方法， 其特征在于， 在发送计费成功消息之后， 还包括： 将所述计费信息记录在所述业务管理平台的离线文件中。 The method according to claim 1, wherein after the sending the charging success message, the method further comprises: recording the charging information in an offline file of the service management platform.
3. 根据权利要求 2所述的方法， 其特征在于， 在将所述计费信息记录在 所述业务管理平台的离线文件之前， 还包括： 所述业务管理平台获知 用户已经成功使用所述计费请求消息对应的业务。 The method according to claim 2, wherein before the charging information is recorded in the offline file of the service management platform, the method further includes: the service management platform knowing that the user has successfully used the meter The service corresponding to the fee request message.
4. 根据权利要求 3所述的方法， 其特征在于， 所述业务管理平台通过以 下方式获知所述用户已经成功使用所述计费请求消息对应的业务： 所述业务管理平台接收来自于业务引擎的计费确认消息； 所述业务管理平台从所述计费确认消息中解析到指示所述用户已 经成功使用所述业务的指示信息。 The method according to claim 3, wherein the service management platform learns that the user has successfully used the service corresponding to the charging request message by: the service management platform receiving the service engine The charging confirmation message is sent by the service management platform from the charging confirmation message to the indication information indicating that the user has successfully used the service.
5. 根据权利要求 2至 4任一项所述的方法， 其特征在于， 在将所述计费 信息记录在所述业务管理平台的离线文件之后， 还包括： 所述预付费 ***获取所述离线文件， 并根据所述离线文件中记录的计费信息进行 补充计费。 The method according to any one of claims 2 to 4, wherein after the charging information is recorded in an offline file of the service management platform, the method further comprises: the prepaid system acquiring the Offline files, and supplementary charging is performed according to the charging information recorded in the offline file.
6. 根据权利要求 1所述的方法， 其特征在于， 还包括 6. The method according to claim 1, further comprising
在业务管理平台接收到来自于业务引擎的计费确认消息时， 所述 业务管理平台监控到所述链路状态为异常状态；  When the service management platform receives the charging confirmation message from the service engine, the service management platform monitors that the link state is an abnormal state;
所述业务管理平台从所述计费确认消息中解析到指示用户未成功 使用对应于所述计费确认消息的业务的指示信息； 緩存对应于所述计费确认消息的退费信息， 并向所述业务引擎发 送退费成功消息。 根据权利要求 6所述的方法， 其特征在于， 在发送所述退费成功消息 之后， 还包括： 将所述退费信息记录在所述业务管理平台的离线文件 中。 根据权利要求 7所述的方法， 其特征在于， 在将所述退费信息记录在 所述业务管理平台的离线文件中之后， 还包括： 所述预付费***获取 所述离线文件， 并才艮据所述离线文件记录的所述退费信息进行补充退 费。 一种预付费业务计费***， 其特征在于， 包括： 业务管理平台和预付 费***， 其中， And the service management platform parses, from the charging confirmation message, indication information indicating that the user does not successfully use the service corresponding to the charging confirmation message; The refund information corresponding to the charging confirmation message is cached, and a refund success message is sent to the service engine. The method according to claim 6, wherein after the sending the refund success message, the method further comprises: recording the refund information in an offline file of the service management platform. The method according to claim 7, wherein after the refund information is recorded in the offline file of the service management platform, the method further includes: the prepaid system acquiring the offline file, and then The supplementary refund is performed according to the refund information recorded by the offline file. A prepaid service billing system, comprising: a service management platform and a prepaid system, wherein
业务管理平台包括：  The business management platform includes:
异常监控模块， 用于实时地监控业务管理平台与预付费***之间 的链路状态， 如果在所述业务管理平台接收到来自于业务引擎的计费 请求消息时， 监控到所述链路状态为异常状态， 则触发緩存模块； 所述緩存模块， 用于緩存对应于所述计费请求消息的计费信息， 并触发通知模块；  An abnormality monitoring module, configured to monitor, in real time, a link state between the service management platform and the prepaid system, and if the service management platform receives the charging request message from the service engine, monitor the link status The buffering module is configured to buffer the charging information corresponding to the charging request message, and trigger the notification module;
所述通知模块， 用于向业务引擎发送计费成功消息； 预付费***包括：  The notification module is configured to send a charging success message to the service engine; the prepaid system includes:
获取模块， 用于从所述緩存模块中获取所述计费信息； 所述补充计费模块， 用于根据所述获取模块获取的所述计费信息 进行补充计费。 才艮据权利要求 9所述的***， 其特征在于，  And an obtaining module, configured to obtain the charging information from the cache module, where the supplementary charging module is configured to perform supplementary charging according to the charging information acquired by the acquiring module. The system of claim 9 wherein:
在业务管理平台接收到来自于业务引擎的计费确认消息时， 所述 异常监控模块监控到所述链路状态为异常状态， 则触发緩存模块； 所述緩存模块，还用于緩存对应于所述计费确认消息的退费信息, 并触发所述通知模块；  When the service management platform receives the charging confirmation message from the service engine, the abnormality monitoring module detects that the link state is abnormal, and triggers a cache module; the cache module is further configured to cache the corresponding Declaring the refund information of the billing confirmation message, and triggering the notification module;
所述通知模块， 还用于向业务引擎发送退费成功消息； 所述获取模块， 还用于从所述緩存模块中获取所述退费信息； 所述预付费***还包括： 补充退费模块， 用于 居所述获取模块 获取的所述退费信息进行补充退费。 The notification module is further configured to send a refund success message to the service engine; The obtaining module is further configured to obtain the refund information from the cache module. The prepaid system further includes: a supplementary refunding module, configured to supplement the refund information acquired by the acquiring module Refund.
PCT/CN2011/070071 2010-06-02 2011-01-07 Charging method and system for prepaid service WO2011150688A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010199242A CN101841800A (en) 2010-06-02 2010-06-02 Prepayment service charging method and system
CN201010199242.X 2010-06-02

Publications (1)

Publication Number Publication Date
WO2011150688A1 true WO2011150688A1 (en) 2011-12-08

Family

ID=42744845

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070071 WO2011150688A1 (en) 2010-06-02 2011-01-07 Charging method and system for prepaid service

Country Status (2)

Country Link
CN (1) CN101841800A (en)
WO (1) WO2011150688A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020036470A1 (en) * 2018-08-17 2020-02-20 삼성전자 주식회사 Billing method and apparatus in wireless communication system

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841800A (en) * 2010-06-02 2010-09-22 中兴通讯股份有限公司 Prepayment service charging method and system
CN102271321A (en) * 2011-07-20 2011-12-07 中兴通讯股份有限公司 prepayment request processing method and device
CN103874044A (en) * 2012-12-17 2014-06-18 中兴通讯股份有限公司 Abnormal billing processing method and abnormal billing processing system
CN106899955B (en) * 2015-12-21 2021-01-22 中兴通讯股份有限公司 Terminal charging method and device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1852096A (en) * 2006-05-08 2006-10-25 中国电信股份有限公司 Method and apparatus for verifying authority and charging between comprehensive management platform and business engine
CN101212532A (en) * 2006-12-30 2008-07-02 中国电信股份有限公司 Combined billing system and method
CN101600185A (en) * 2009-07-14 2009-12-09 中国联合网络通信集团有限公司 Booking method, system and the Business Management Platform of across a network territory value-added service set meal
CN101707525A (en) * 2009-09-18 2010-05-12 中兴通讯股份有限公司 Charging method and device
CN101841800A (en) * 2010-06-02 2010-09-22 中兴通讯股份有限公司 Prepayment service charging method and system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1852096A (en) * 2006-05-08 2006-10-25 中国电信股份有限公司 Method and apparatus for verifying authority and charging between comprehensive management platform and business engine
CN101212532A (en) * 2006-12-30 2008-07-02 中国电信股份有限公司 Combined billing system and method
CN101600185A (en) * 2009-07-14 2009-12-09 中国联合网络通信集团有限公司 Booking method, system and the Business Management Platform of across a network territory value-added service set meal
CN101707525A (en) * 2009-09-18 2010-05-12 中兴通讯股份有限公司 Charging method and device
CN101841800A (en) * 2010-06-02 2010-09-22 中兴通讯股份有限公司 Prepayment service charging method and system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020036470A1 (en) * 2018-08-17 2020-02-20 삼성전자 주식회사 Billing method and apparatus in wireless communication system

Also Published As

Publication number Publication date
CN101841800A (en) 2010-09-22

Similar Documents

Publication Publication Date Title
EP2297986B1 (en) Synchronizing real-time and off-line accounts for communications
JP5709850B2 (en) Fault tolerant method for generating fully correlated IMS billing data records
US20140087775A1 (en) Redirection method and redirection apparatus under policy and charging control
CN107079043B (en) Device and method for offline charging
US20110161248A1 (en) Online charging correlation in ims networks
JP6576441B2 (en) Non-linear data billing
WO2011150688A1 (en) Charging method and system for prepaid service
JP7108628B2 (en) Online charging mechanism while OCS is unresponsive
CN110880981B (en) Gx session exception handling method and device
US20190305975A1 (en) Aggregated handling of quota in a network node
WO2009062408A1 (en) Method for implementing value-added service and service control point
WO2011047568A1 (en) Method and device for sending charging data recording
WO2009149610A1 (en) Method and apparatus for online charging
BRPI0615719B1 (en) METHOD FOR OPERATING GROUP SERVICES IN A COMMUNICATION NETWORK AND PROVISION FOR OPERATING A GROUP SERVICE OR VARIOUS GROUP SERVICES IN A COMMUNICATION NETWORK
CN104717627A (en) Billing ticket establishing method, data service billing method and related device
EP2706768B1 (en) User transfer control method and service control point
WO2005104578A1 (en) Providing information on services in a communication system
US11765278B2 (en) Replay agent for delivering charging event messages from a message broker in a mobile telecommunications network
CN110300235A (en) A kind of communication service billing method and device
KR100833292B1 (en) System and method for backup charging data in real time in mobile communication network
WO2012089000A1 (en) Method, gateway and communication system for charging post-paying user
KR100802092B1 (en) Method and system for billing based on the client-server
CN101232634A (en) Data synchronization method, system and device
US20140378093A1 (en) Synchronizing charging for telecommunication service with notification of applicable tariff
EP2101442A1 (en) Charging processing method, service network element and charging system thereof

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

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

Country of ref document: EP

Kind code of ref document: A1