WO2005011194A1 - Procede de mise en oeuvre de compte et systeme de compte - Google Patents

Procede de mise en oeuvre de compte et systeme de compte Download PDF

Info

Publication number
WO2005011194A1
WO2005011194A1 PCT/CN2004/000884 CN2004000884W WO2005011194A1 WO 2005011194 A1 WO2005011194 A1 WO 2005011194A1 CN 2004000884 W CN2004000884 W CN 2004000884W WO 2005011194 A1 WO2005011194 A1 WO 2005011194A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
charging
attribute
charged
identifier
Prior art date
Application number
PCT/CN2004/000884
Other languages
English (en)
French (fr)
Inventor
Xiaozheng Guo
Zhijian Lu
Xin Zhang
Qingchen Zhu
Youkun Chen
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.
Priority to US10/566,952 priority Critical patent/US7526075B2/en
Publication of WO2005011194A1 publication Critical patent/WO2005011194A1/zh

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/66Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method and a charging system for implementing charging. Background of the invention
  • each charging processing module is combined to form a charging processing part.
  • service 1 applies for charging.
  • the service processing section performs necessary pre-charging processing on service 1, and then the charging processing section The charging processing module of service 1 is called, and the charging processing module of service 1 performs charging processing on service 1.
  • service 2 applies for charging.
  • the service processing section Service 2 performs necessary pre-charging processing, and then the charging processing section calls the charging processing module of service 2, and the charging processing module of service 2 performs charging processing on service 2.
  • service 3 applies for charging.
  • the service processing section performs necessary charging for service 3 Pre-processing, then the charging processing module of the service 3 calls the charging processing module of the service 3, and the charging processing module of the service 3 performs charging processing on the service 3.
  • the upgrade of the billing system is generally completed by the billing system developer.
  • the developer completes the upgrade of the existing billing system by modifying the existing billing processing part or adding a new billing processing module. Will cause the following disadvantages:
  • An object of the present invention is to provide a method for realizing charging and a charging system based on implementing the charging method of the present invention.
  • the present invention provides a method for implementing charging, which includes: a. Establishing a correspondence between a service attribute of a service to be charged and a charging rule of the service to be charged;
  • the service attribute includes at least a service identifier and a service charging type.
  • Step a includes:
  • Step C includes:
  • the service charging type, and the service charging attribute should include the correspondence between field names, and obtain the service charging attribute of the service to be charged from the service identifier and service charging type of the service to be charged. Contains field names;
  • the charging rule of the service to be charged is obtained from the service charging attribute of the service to be charged.
  • step al includes:
  • Step c includes:
  • obtaining the service charging attribute of the to-be-charged service should include a field name
  • the field name should be included, and the service charging attribute of the service to be charged should include the field name to determine the service charging attribute of the service to be charged.
  • the charging rule of the service to be charged is obtained from the service charging attribute of the service to be charged.
  • step all includes: al ll, establish a correspondence between a service identifier and a service charging category; al l2, establish a correspondence between a service charging category, a service charging type, and selecting a service charging attribute identifier.
  • the correspondence between the service identifier and the service charging category includes: the correspondence between the service identifier, the service charging category, and discount information;
  • the discount information includes periodic discounts and usage discount information.
  • the correspondence between the service charging category, the service charging type, and the selected service charging attribute identifier includes:
  • the auxiliary charging rule includes a minimum charging standard for usage and a rounding standard for usage.
  • the correspondence between the service charging attribute and the charging rule described in step a2 is recorded in a table form; the correspondence between the selection of the service charging attribute identifier and the field names that the service charging attribute should include in step a2 is described in a table form recording.
  • the correspondence table between the service charging attribute and the charging rule is a sub-table for selecting a correspondence table between a service charging attribute identifier and a field name that the service charging attribute should include, and the service charging attribute identifier is used to identify each other.
  • the fields related to the service charging attributes in the correspondence table between the service charging attributes and the charging rules correspond to the fields in the mapping table between the service charging attribute identifier and the field names that the service charging attributes should contain.
  • the number of fields in the correspondence table between the service charging attribute and the charging rule, and the corresponding relationship table of the selected service charging attribute identifier and the field name that the service charging attribute should contain are greater than any service charging attribute Number of fields.
  • the method further includes:
  • the corresponding relationship table between the service charging attributes and the charging rule and the field names that the service charging attribute identifier and the service charging attribute should contain The correspondence table adds column information to the corresponding records.
  • Step C includes:
  • the service charging type and the selected service charging attribute identifier includes the service charging category of the service to be charged and the charging rule corresponding to the service charging type, Determine whether it is necessary to obtain service charging attributes, and if so, perform step c91; otherwise, perform step c95;
  • Step d includes:
  • the present invention also provides a charging system based on implementing the above charging method.
  • the system includes: a charging rule obtaining module: acquiring a charging rule corresponding to a service to be charged according to a service attribute of the service to be charged, and charging the charging The rules are transmitted to the billing processing module;
  • Accounting processing module performs accounting processing on accounting services according to the transmitted accounting rules.
  • the acquiring charging rule module includes:
  • Obtaining a service charging category submodule configured to obtain a discount and a service charging category corresponding to the service to be charged according to a service identifier in a service attribute of the service to be charged; and output the discount to the charging processing module Output the service charging category to a discrimination submodule;
  • the discrimination submodule is configured to: according to the received service charging category, determine the correspondence relationship between the charging category, the service charging type, and selecting a service charging attribute identifier Whether the charging rule corresponding to the service to be charged is included to determine whether the service charging attribute needs to be obtained; if not, the submodule for obtaining the service charging rule is notified that the service charging attribute of the service to be charged is not required to be obtained; Notify that the service charging attribute sub-module needs to obtain the service charging attribute of the service to be charged;
  • Obtaining the service charging attribute sub-module When receiving the notification of the service charging attribute for the service to be charged, the service charging type, the service charging type, and the corresponding relationship for selecting the service charging attribute identifier are used to obtain the to-be-accounted Select the service charging attribute identifier and auxiliary charging rules corresponding to the toll service; obtain the field name that the service charging attribute should contain according to the selected service charging attribute identifier; obtain the service charging attribute according to the field name that the service charging attribute should contain; Transmitting auxiliary charging rules to a charging processing module; transmitting service charging attributes to a submodule for obtaining charging rules;
  • Obtaining a service charging rule submodule When receiving a notification of a service charging attribute that does not require obtaining a service to be charged, obtain the service charging type from the corresponding relationship between the service charging type, the service charging type, and the selected service charging attribute identifier. The charging rule corresponding to the charging service and transmits the obtained charging rule to the charging processing module; when the service charging attribute is received, charging from the service is performed A charging rule is acquired from a correspondence between the attribute and the charging rule, and the acquired charging rule is transmitted to the charging processing module.
  • the present invention when a new service needs to be developed or the charging method of an existing service needs to be modified, there is no need to upgrade the charging processing module that is the core of the charging system, and only the services provided to the charging processing module are required.
  • the corresponding modification of the information can meet the charging requirements of various services; the charging processing module of the charging system has nothing to do with starting new services or changing the charging method of the existing services.
  • FIG. 1 is a schematic diagram showing a method for implementing charging in the prior art
  • FIG. 2 is a schematic diagram showing a correspondence between a table S and a table P of the present invention
  • FIG. 3 is a flowchart of implementing charging in an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a charging system of the present invention. Mode of Carrying Out the Invention
  • the charging processing module of the charging system when a new service is added or the charging method of the original service is changed, the charging processing module of the charging system does not need to be modified and upgraded, and only the service information to be provided to the charging system is changed.
  • the billing processing module of the billing system has nothing to do with services, and a set of billing systems can be used to meet existing and future billing requirements for various services.
  • the charging processing module in the charging system provided by the present invention has nothing to do with services.
  • different charging rules and other charging are provided to the charging processing module for different services.
  • the charging processing module according to the provided charging rules The billing processing information and other billing-related information are used to charge the service, thereby ensuring the stability of the billing processing module, and achieving the purpose that the billing processing module has nothing to do with the service.
  • the use of the billing system provided by the present invention can save manpower, economics, and time overhead caused by upgrading the billing processing module, thereby reducing the cost of the billing system, and the billing processing module does not need to be upgraded, reducing Unstable and unreliable factors of the billing system.
  • service attributes are related information carried by the service to be charged, including at least a service identifier, a service charging type, and other related service information;
  • the service side generates a service identifier for the service that the user needs to use according to the user registration situation.
  • the service attribute of the service is determined according to the user's use situation.
  • the service The attributes include at least service charging attributes, and also include information such as calling number, called number, transfer number, call duration, service charging type, and service identification;
  • the service attributes of each to-be-charged service are used to determine the charging rules for each to-be-charged service.
  • the charging rule is provided to the charging processing module, and the charging processing module performs charging processing for each to-be-charged service according to the provided charging rules for each to-be-charged service and other information when the user uses the service, thereby implementing charging
  • the system has no business purpose.
  • the correspondence between the service charging attributes and the charging rules is recorded in the form of a table
  • the corresponding relationship between the service identifier, the service charging type, and the service charging attribute should include the field name is determined.
  • the service charging attribute of the charging service should include the field name; according to the field name that the service charging attribute of the service to be charged should include, determine the service charging attribute of the service to be charged from the service attribute to be charged;
  • the charging rule of the service to be charged is determined from the corresponding relationship between the service charging attribute and the charging rule.
  • the second specific implementation manner of implementing the charging method of the present invention is as follows: For the establishment of the service identifier, the type of service charging, and the attribute of the service charging described in the first specific implementation manner, the correspondence relationship between field names should be included In this embodiment, the following manners can be implemented:
  • the correspondence between the selection of the service charging attribute identifier and the service charging attribute should include the field name is recorded in the form of a table
  • the service identifier, the service charging type, and the selection are selected.
  • the selected service charging attribute identifier of the service to be charged is determined in the correspondence between the service charging attribute identifiers;
  • the charging rules of the to-be-charged service are provided to the charging processing module, and the charging processing module charges the charging service according to the provided charging rule, thereby achieving the purpose that the charging processing module has nothing to do with the service.
  • a third specific implementation manner for implementing the charging method of the present invention is as follows: In this implementation manner, the establishment of a service identifier, a service charging type, and selection in the second specific implementation manner of the present invention can be implemented in the following manner. Correspondence of service charging attribute identification:
  • the correspondence between the service identifier and the service charging category, and the correspondence between the service charging category, the service charging type, and the selected service charging attribute identifier are recorded in the form of a table, respectively;
  • the correspondence table between the service identifier and the service charging category includes the correspondence between the service identifier, the service charging category, and discount information.
  • the discount information includes periodic discounts, usage discounts, and discount-related information.
  • the table includes: the corresponding relationship between the service charging category, the service charging type, the selected service charging attribute identifier, the charging rule, and the auxiliary charging rule; wherein the auxiliary charging rule includes the minimum charging standard of the usage amount and the usage amount. Rounding standards, etc.
  • the correspondence table between service charging category, service charging type, and selection of service charging attribute identifier is Table A; the correspondence table between selecting service charging attribute identifier and service charging attribute should include field names is Table S; service The correspondence table between the charging attributes and the charging rules is Table P. Among them, Table P is a sub-table of Table S. By analyzing the number of fields that the service charging attributes of the existing services should contain, a sufficient number of fields are defined in Table S. Number of columns. The number of columns related to the service charging attribute field name in Table S should be greater than the number of fields included in the service charging attribute of any existing service. The number of columns in Table S should also be greater than the service charging of future services. The number of fields included in the attribute.
  • the number of columns in Table S should also be greater than the number of fields that the service charging attribute should contain after modifying the service charging attribute of the original service.
  • the number of columns in table S is defined in such a way that when the service charging attribute of the original service needs to add fields, only the record of the service charging attribute of the original service that needs to be added is queried in table S, and here It is sufficient to add a list of information to the record; for example, for the IP phone dialing service, the original calling number and the called number are used as the service charging attribute for charging. To modify the calling number, called number, and transfer number, you can add a list of transfer number information to the original record without modifying the structure of Table S; therefore, when new services are needed, only the A new record is added in Table S.
  • This record includes the field names that should be included in the service charging attribute of the newly launched service.
  • the value of the selected service charging attribute identification field of this record is the same as the selection contained in the related record in Table A.
  • the value of the service charging attribute ID correspond
  • the service billing attributes in Table S should contain the corresponding relationship between the field names and the relevant fields of the service billing attributes in Table P as shown in Figure 2.
  • Numbers correspond to different charging rules, for example, the calling number and called number are 010 and 021, respectively, and the corresponding charging rule is IPP-A; the calling number and called number are 010, 022, and the corresponding charging The rule is IPP_B; the calling and called numbers are 021 and 0317 respectively, and the corresponding charging rules are IPP-C; the charging rules of calling and called numbers respectively 010 and 022 can also be modified as required IPP-A. Similarly, the charging rules corresponding to all calling numbers and called numbers can be modified to IPP_A as required.
  • the service side is responsible for establishing a service usage information table, and the service usage information table records information related to a user's business, and the related information includes at least service charging attributes.
  • the service usage information table is modified or added according to the need to modify the service charging attribute information accordingly.
  • different service usage information tables can be established according to different service charging attribute information, and related information of the service to be charged with different service charging attributes is stored in the corresponding service usage information table; or Only one service usage information table is established, and the related information of the to-be-charged services with different service charging attributes is stored in one service usage information table.
  • the IP phone service generates a service identifier SERVICE_IP1, and the service identifier SERVICE_IP1 corresponds to the IP phone service whose service charging category applied by USER-A is IP1, and stores the relevant information registered by USER-A in table T
  • the table T contains the service identifier SERVICE-IP 1, the user identifier USER_A, the service charging category IP1, and discount information, etc .; the discount information includes the periodic discounts enjoyed by the user, the usage discount, and discount-related information;
  • step 300 when the user USER-A uses the IP telephone service with the service charging category IP1, the service side generates a usage event according to the use of the IP telephone service by USER_A; the event identifier is EVENT-A, The user USER- A uses the service charge category IP1 IP phone service related information to be recorded by the event; then, step 310 is performed;
  • the type of the usage event is a service charging type
  • the event type of the IP telephony service whose service charging category used by user USER_A is IP1 is the usage type
  • This event contains information about the IP phone service of user USER-A using the service charging category of IP1.
  • the start time 2001-01-01 00: 00: 00
  • the end time 2001-01-01 01 : 00: 00
  • user identifier USER-A user identifier USER-A
  • service identifier SERVICE-IP service identifier
  • the service side writes the relevant service information into the service use information table according to the requirements in the service use information table provided by the event, such as the calling number is 010 and the called number is 021.
  • step 310 after obtaining the service identifier SERVICE_IP1 from the event, step 320 is performed, and according to the service identifier SERVICE_IP1, a phase ID corresponding to the service identifier is obtained from table T.
  • step 330 is performed, according to the service charging category IP1 and the event type as a usage type, to find from Table A whether the record corresponding to IP1 and the usage type contains a charging rule If it contains a charging rule, step 340 is performed to obtain a charging rule and an auxiliary charging rule, and then step 350 is performed;
  • step 330 if the charging rule is not included, step 331 is performed to obtain the selected service charging attribute identifier and the auxiliary charging rule in the record, and then step 332 is performed according to the obtained selected service charging attribute identifier in the table.
  • step 331 is performed to obtain the selected service charging attribute identifier and the auxiliary charging rule in the record, and then step 332 is performed according to the obtained selected service charging attribute identifier in the table.
  • Look up the corresponding record in S and obtain the field names included in the service charging attributes in the record, such as the calling number and the called number; according to the field names included in the obtained service charging attributes, search in the service usage information table provided by the event
  • the service charging attributes are 010 and 021; then step 333 is performed, and according to the service charging attributes 010 and 021, the charging rules corresponding to 010 and 021 are obtained from the table P, and then step 350 is performed;
  • the auxiliary charging rules are a minimum charging standard for usage, a rounding standard for usage, and the like.
  • step 350 according to the relevant information of the service to be charged, such as the start use time, end use time, discount information, and auxiliary accounting.
  • the charging rules and the charging rates corresponding to the to-be-charged services included in the charging rules are used to charge the to-be-charged services, thereby achieving the purpose that the charging system has nothing to do with services.
  • the present invention further provides a charging system based on implementing the foregoing charging method.
  • 400 is a charging system provided by the present invention, and the charging system 400 includes: obtaining a charging rule module 410 and a charging processing module 420;
  • the obtaining charging rule module 410 obtains the charging rules, discounts and auxiliary charging rules of the to-be-charged services according to the service attributes of the to-be-charged services; and transmits the charging rules, discount information and auxiliary charging rules of the to-be-charged services to Billing processing module 420;
  • the charging processing module 420 performs charging processing for the to-be-charged service according to the charging rule, discount information, and auxiliary charging rules of the to-be-charged service transmitted from the obtaining charging rule module 410.
  • the obtaining charging rule module 410 includes: obtaining a service charging category sub-module 430, a discrimination sub-module 440, obtaining a service charging attribute sub-module 450, and obtaining a charging rule sub-module 460; wherein the obtaining service charging category sub-module 430 According to the service identifier in the service attribute of the service to be charged, the service charging category and discount information corresponding to the service to be charged are obtained, the obtained discount information is transmitted to the charging processing module 420, and the obtained service charging type is transmitted to Discrimination sub-module 440;
  • the judging submodule 440 judges the service charging type, the service charging type, and selects a service account according to the service charging type carried by the service attribute of the service to be charged and the service charging type transmitted from the obtaining service charging category submodule 430
  • the charge attribute identifier corresponds to whether the service charging type of the service to be charged and the charging rule corresponding to the service charging category are included. If the charging rule is included, the "No need to obtain the selected service charging attribute" identifier is transmitted to the acquisition account.
  • Fee rule sub-module 460 if it does not contain a charging rule, "require the acquisition of service charging attributes of the service to be charged" to the acquisition service charging attribute sub-module 450;
  • Obtaining the service charging attribute sub-module 450 When receiving the "service charging attribute for which a service to be charged needs to be obtained" transmitted from the determination sub-module 440, select the service charging attribute identifier from the service charging category, service charging type, and In the correspondence relationship, the selected service charging attribute identifier and the auxiliary charging rule corresponding to the service to be charged are acquired; the auxiliary charging rule is transmitted to the charging processing module 420; and the service charging attribute is obtained according to the selected service charging attribute identifier.
  • the rule submodule 460 receives the identification of "No need to obtain the selected service charging attribute" transmitted from the determination submodule 440, it obtains the waiting information from the service charging category, the service charging type, and the corresponding relationship of the selected service charging attribute identifier.
  • the charging rules and auxiliary charging rules corresponding to the charging service are transmitted to the charging processing module 420; when the charging rule sub-module is obtained 460 receives the service charging property acquisition sub-module 450 to transmit the service charging genus
  • the charging processing module 420 When the nature, according to the business charging attributes from the corresponding relationship between the business charging attributes and charging rules to obtain their corresponding charging rules, and transmit them to the charging processing module 420;
  • the accounting processing module 420 performs accounting on the accounting service according to the transmitted accounting rules, discount information, and auxiliary accounting rules.

Description

一种实现计费的方法及计费系统
技术领域
本发明涉及网络通信技术领域, 具体涉及一种实现计费的方法及计 费系统。 发明背景
随着计算机的迅速发展, 计算机已经成为人们工作、 生活中不可或 缺的工具。 国际互联网也随着计算机的发展而深入到我们的生活中。 人 们利用计算机上网, 通过国际互联网进行通讯、 娱乐、 工作。 在人们通 过国际互联网实现计算机上网或拨打 IP电话的时侯,对提供国际互联网 服务的运营商来说, 计费是一项非常重要的工作。
目前现有的计费系统, 由于每种业务在计费时的业务属性不同, 因 此, 需要分别针对不同业务属性的计费业务设置不同的费率, 由不同的 计费处理模块分别对其进行处理, 各个计费处理模块合在一起形成一个 计费处理部分。
当需要对业务进行计费处理时, 针对业务属性不同的业务, 需要调 用不同的计费处理模块。 如附图 1所示, 在图 1中, 业务 1申请计费, 当需要为业务 1进行计费处理时, 由业务处理部分对业务 1进行必要的 计费前处理, 然后由计费处理部分调用业务 1的计费处理模块, 由业务 1的计费处理模块对业务 1进行计费处理; 同理, 业务 2申请计费, 当 需要为业务 2进行计费处理时, 由业务处理部分对业务 2进行必要的计 费前处理, 然后由计费处理部分调用业务 2的计费处理模块, 由业务 2 的计费处理模块对业务 2进行计费处理; 同理, 业务 3申请计费, 当需 要为业务 3进行计费处理时, 由业务处理部分对业务 3进行必要的计费 前处理, 然后由计费处理部分调用业务 3的计费处理模块, 由业务 3的 计费处理模块对业务 3进行计费处理。
上述现有的计费系统, 虽然能满足运营商现在开展的业务, 但是, 随着人们需求的变化、 市场经济的激烈竟争, 运营商为了提高自己的竟 争能力, 会推出更多的计费规则或者改变现有业务的计费规则, 以吸引 更多的用户使用自己提供的服务, 例如改变现有 IP 电话业务的计费方 式, 如: 原有 IP电话业务按主叫号码和被叫号码计费, 现在 IP电话业 务需要按主叫号码 +被叫号码 +转接号码计费。 当运营商需要推出新业务 或者需要改变现有业务的计费规则时, 现有的计费系统往往就不能满足 运营商的要求了, 具体表现在:
为了满足运营商开展新业务或改变现有业务的计费规则的要求, 需 要升级计费系统。 升级计费系统的工作一般由计费系统开发商来完成, 开发商通过对现有计费处理部分进行修改或增加新的计费处理模块, 完 成对现有的计费系统的升级, 该升级会造成如下缺点:
( 1 )、 对现有的计费系统进行升级, 需要运营商投入大量的人力、 物力和时间, 而且对现有的计费系统升级还增加了整个计费系统的不稳 定因素和不可靠因素;
( 2 )、 计费系统的开发商为了开发出满足运营商业务要求的系统, 在计费系统开发完成后还需要进行完善性测试, 即在计费系统开发完成 之后, 为了保证整个计费系统的质量, 计费系统开发商还要在运营商处 做实验局开局等活动, 如果在实验局开局过程中, 计费系统出现错误, 还需要计费系统开发商进行返工修改;
( 3 )、 当计费系统开发商将最终的计费系统提交给运营商后, 运营 商还要对计费系统进行验收, 组织计费系统维护人员进行培训。
由此可见, 由于对现有计费系统的升级和修改, 延长了运营商开展 新业务的准备时间, 甚至会因此而使运营商在市场竟争中由于延误时机 而处于下风。
综上所述, 现有的计费系统由于与业务的耦合度强, 使计费系统成 本高、 稳定性和可靠性差、 适用范围局限。 发明内容
本发明的目的在于, 提供一种实现计费的方法及基于实现本发明计 费方法的计费系统, 当需要开展新的业务或对原有业务的计费方法进行 修改时, 不需要调整计费处理模块, 只需要将提供给计费系统的业务信 息做相关的修改即可, 使计费系统与业务无关, 实现了降低计费系统成 本、 提高计费系统的稳定性、 可靠性及通用性的目的。
为达到上述目的,本发明提供了一种实现计费的方法,该方法包括: a、建立待计费业务的业务属性与该待计费业务的计费规则的对应关 系;
b、 当需要对待计费业务进行计费时,获取所述待计费业务的业务属 性;
c、根据业务属性与计费规则的对应关系, 由所述待计费业务的业务 属性获取所述该待计费业务的计费规则;
d、根据获取的待计费业务的计费规则,统一对所述待计费业务进行 计费处理。
其中, 所述业务属性至少包括业务标识和业务计费类型。
其中, 步骤 a包括:
al、 建立业务标识、 业务计费类型与业务计费属性应包含字段名称 的对应关系;
a2、 建立业务计费属性与所述计费规则的对应关系。 其中, 步骤 C包括:
cl、 根据业务标识、 业务计费类型与业务计费属性应包含字段名称 的对应关系, 由待计费业务的业务标识和业务计费类型, 获取所述待计 费业务的业务计费属性应包含字段名称;
c2、 根据所述待计费业务的业务计费属性应包含字段名称, 确定所 述待计费业务的业务计费属性;
c3、 根据业务计费属性与计费规则的对应关系, 由所述待计费业务 的业务计费属性获取所述待计费业务的计费规则。
其中, 步骤 al包括:
al l、建立业务标识、 业务计费类型以及选择业务计费属性标识的对 应关系;
al2、建立选择业务计费属性标识与所述业务计费属性应包含字段名 称的对应关系。
其中, 步骤 c包括:
c4、 根据业务标识、 业务计费类型以及选择业务计费属性标识的对 应关系, 由所述待计费业务的业务标识和业务计费类型获取所述待计费 业务的选择业务计费属性标识;
c5、 根据所述待计费业务的选择业务计费属性标识, 获取所述待计 费业务的业务计费属性应包含字段名称;
c6、 根据选择业务计费属性标识与业务计费属性应包含字段名称的 对应关系, 由所述待计费业务的业务计费属性应包含字段名称确定所述 待计费业务的业务计费属性;
c7、 根据业务计费属性与计费规则的对应关系, 由所述待计费业务 的业务计费属性获取所述待计费业务的计费规则。
其中, 步骤 al l包括: al l l、 建立业务标识与业务计费类别的对应关系; al l2、 建立业务计费类别、 业务计费类型以及选择业务计费属性标 识的对应关系。
其中, 所述业务标识与业务计费类别的对应关系包括: 所述业务标 识、 业务计费类别以及折扣信息的对应关系;
其中, 折扣信息包括周期性折扣及使用量折扣信息。
其中, 所述业务计费类别、 业务计费类型以及选择业务计费属性标 识的对应关系包括:
业务计费类别、 业务计费类型、 选择业务计费属性标识、 计费规则 以及辅助计费规则的对应关系;
其中, 所述的辅助计费规则包括使用量的最小计费标准、 使用量圓 整标准。
其中,步骤 a2所述业务计费属性与计费规则的对应关系以表的形式 记录; 步骤 al2所述选择业务计费属性标识与业务计费属性应包含的字 段名称的对应关系以表的形式记录。
其中, 所述的业务计费属性与计费规则的对应关系表是选择业务计 费属性标识与业务计费属性应包含的字段名称的对应关系表的子表, 且 通过业务计费属性标识相互关联;
所述的业务计费属性与计费规则的对应关系表中的与业务计费属性 相关字段——对应于选择业务计费属性标识与业务计费属性应包含的 字段名称的对应关系表中的业务计费属性应包含的字段名称的相关字 段。
其中, 所述业务计费属性与计费规则的对应关系表和所述的选择业 务计费属性标识与业务计费属性应包含的字段名称的对应关系表的字 段数分别大于任意业务计费属性的字段数。 其中, 该方法进一步包括:
当业务计费属性应包含的字段名称需要增加时, 所述的业务计费属 性与计费规则的对应关系表和所述的选择业务计费属性标识与业务计 费属性应包含的字段名称的对应关系表在相应的记录中增加列信息。
其中, 步骤 C包括:
c8、 根据业务标识与业务计费类别的对应关系, 由所述待计费业务 的业务标识获取所述待计费业务的业务计费类别和折扣;
c9、 根据所述的业务计费类别、 业务计费类型与选择业务计费属性 标识的对应关系中是否包括所述待计费业务的业务计费类别、 业务计费 类型对应的计费规则, 判断是否需要获取业务计费属性, 如果是, 则执 行步骤 c91, 否则执行步骤 c95 ;
c91、根据业务计费类别、业务计费类型以及选择业务计费属性标识 的对应关系, 获取所述的业务计费类别、 业务计费类型对应的选择业务 计费属性标识和辅助计费规则;
c92、根据所述待计费业务的选择业务计费属性标识获取所述待计费 业务的业务计费属性应包含的字段名称;
c93、根据所述待计费业务的业务计费属性应包含的字段名称获取所 述待计费业务的业务计费属性;
c94、根据所述待计费业务的业务计费属性获取所述待计费业务的计 费规则;
c95、获取所述的业务计费类别、业务计费类型对应的计费规则和辅 助计费规则。
其中, 步骤 d包括:
根据所述计费规则、 折扣信息和辅助计费规则对所述待计费业务进 行计费处理。 本发明还提供一种基于实现上述计费方法的计费系统,该系统包括: 获取计费规则模块: 根据待计费业务的业务属性获取待计费业务对 应的计费规则, 将该计费规则传输至计费处理模块;
计费处理模块:根据传输来的计费规则对待计费业务进行计费处理。 其中, 所述获取计费规则模块包括:
获取业务计费类别子模块: 用于根据待计费业务的业务属性中的业 务标识获取所述待计费业务对应的折扣和业务计费类别; 将所述折扣输 出到所述计费处理模块; 将所述的业务计费类别输出到判别子模块; 判别子模块: 用于根据接收到的业务计费类别, 由计费类别、 业务 计费类型以及选择业务计费属性标识的对应关系中是否包含待计费业 务对应的计费规则判断是否需要获取业务计费属性; 如果不需要, 则通 知获取业务计费规则子模块不需要获取待计费业务的业务计费属性, 如 果需要, 则通知获取业务计费属性子模块需要获取待计费业务的业务计 费属性;
获取业务计费属性子模块: 当接收到需要获取待计费业务的业务计 费属性通知时, 从业务计费类别、 业务计费类型以及选择业务计费属性 标识的对应关系中, 获取待计费业务对应的选择业务计费属性标识和辅 助计费规则; 根据选择业务计费属性标识获取业务计费属性应包含的字 段名称; 根据业务计费属性应包含的字段名称获取业务计费属性; 将辅 助计费规则传输至计费处理模块; 将业务计费属性传输至获取计费规则 子模块;
获取业务计费规则子模块: 当接收到不需要获取待计费业务的业务 计费属性通知时, 从业务计费类别、 业务计费类型以及选择业务计费属 性标识的对应关系中, 获取待计费业务对应的计费规则并将获取的计费 规则传输至所述计费处理模块; 当接收到业务计费属性时, 从业务计费 属性与计费规则的对应关系中获取计费规则, 将获取的计费规则传输至 所述计费处理模块。
利用本发明, 当需要开展新的业务或对原有业务的计费方法进行修 改时, 不需要对作为计费系统核心的计费处理模块进行升级, 只需要对 提供给计费处理模块的业务信息进行相应修改, 即可满足各类业务的计 费要求; 计费系统的计费处理模块与开展新业务或改变原有业务的计费 方法无关, 使用一套计费处理模块即可满足现有各类业务及将来需要开 展的各类业务的计费要求, 减少了计费系统的不稳定因素和不可靠因 素,从而实现了降低计费系统的成本,提高计费系统的稳定性, 可靠性, 应用广泛性的目的。 附图简要说明
图 1为显示现有技术中实现计费的方法的示意图;
图 2为显示本发明表 S和表 P对应关系的示意图;
图 3是本发明一实施例中实现计费的流程图;
图 4是本发明的计费系统示意图。 实施本发明的方式
在本发明中, 当新增业务或改变原有业务的计费方法时, 计费系统 的计费处理模块不需要进行修改和升级, 只需要将要提供给计费系统的 业务信息做相关的改动, 计费系统的计费处理模块与业务无关, 使用一 套计费系统即可满足现有和将来各类业务的计费要求。
本发明所提供的计费系统中的计费处理模块与业务无关, 使用该计 费系统对不同业务进行计费时, 针对不同的业务为计费处理模块提供不 同的计费规则及其它计费相关信息, 计费处理模块根据提供的计费规则 及其它计费相关信息对业务进行计费处理, 从而保证计费处理模块的稳 定性, 实现了计费处理模块与业务无关的目的。
使用本发明所提供的计费系统能够节省因对计费处理模块升级而造 成的人力、 经济和时间上的开销, 从而降低了计费系统的成本, 而且计 费处理模块不需要升级, 减少了计费系统的不稳定因素和不可靠因素。
下面对本发明进行详细描述。
(一) 实现本发明计费方法的第一种具体实施方式如下:
建立业务属性与计费规则的对应关系; 其中, 业务属性为待计费业 务所承载的相关信息, 至少包括业务标识、 业务计费类型, 还可包括其 它相关业务信息;
业务侧根据用户注册的情况为用户需要使用的业务生成业务标识, 当用户使用该业务标识对应的业务,如进行 IP电话拨叫等,根据用户使 用情况确定此次业务的业务属性, 其中, 业务属性至少包括业务计费属 性, 还包括主叫号码、 被叫号码、 转接号码、 通话时长、 业务计费类型、 业务标识等信息;
记录用户使用业务时的其它信息, 如通话开始时间、 通话结束时间 等, 当需要为用户使用的业务进行计费时, 用户使用的业务成为待计费 业务;
针对不同的待计费业务, 按照已经建立的业务属性与计费规则的对 应关系, 由各个待计费业务的业务属性确定各个待计费业务的计费规 则, 将各个待计费业务的计费规则提供给计费处理模块, 计费处理模块 根据提供的各个待计费业务的计费规则以及用户使用业务时的其它信 息, 为各个待计费业务进行计费处理, 从而实现了计费系统与业务无关 的目的。
其中, 上述具体实施方式中建立业务属性与计费规则的对应关系可 以通过如下方式实现:
建立业务标识、 业务计费类型以及业务计费属性应包含字段名称的 对应关系; 以及建立业务计费属性与计费规则的对应关系;
其中, 在本发明实施例中, 业务计费属性与计费规则的对应关系以 表的形式记录;
其中, 如上所述针对不同的待计费业务确定各个待计费业务的计费 规则的具体实现为:
当需要为待计费业务进行计费时, 根据待计费业务的业务标识和业 务计费类型, 从业务标识、 业务计费类型、 以及业务计费属性应包含字 段名称的对应关系中确定待计费业务的业务计费属性应包含字段名称; 根据待计费业务的业务计费属性应包含的字段名称, 从待计费业务 属性中确定待计费业务的业务计费属性;
根据待计费业务的业务计费属性, 从业务计费属性和计费规则的对应关 系中确定待计费业务的计费规则。
(二) 实现本发明计费方法的第二种具体实施方式如下: 对于第一种具体实施方式中所述的建立业务标识、 业务计费类型、 以及业务计费属性应包含字段名称的对应关系, 在本实施例中可以通过 如下方式实现:
建立业务标识、 业务计费类型以及选择业务计费属性标识的对应关 系; 以及建立选择业务计费属性标识与业务计费属性应包含字段名称的 对应关系。
其中, 选择业务计费属性标识与业务计费属性应包含字段名称的对 应关系以表的形式记录;
在本发明实施例中, 当需要为待计费业务进行计费时, 根据待计费 业务的业务标识和业务计费类型, 从业务标识、 业务计费类型以及选择 业务计费属性标识的对应关系中确定待计费业务的选择业务计费属性 标识;
根据待计费业务的选择业务计费属性标识, 从选择业务计费属性标 识与业务计费属性应包含的字段名称的对应关系中, 确定待计费业务的 业务计费属性包含的字段名称;
根据待计费业务的业务计费属性应包含的字段名称 , 从待计费业务 属性中确定待计费业务的业务计费属性;
根据待计费业务的业务计费属性, 从业务计费属性和计费规则的对 应关系中确定待计费业务的计费规则;
将待计费业务的计费规则提供给计费处理模块, 由计费处理模块按 照提供的计费规则对待计费业务进行计费, 从而实现了计费处理模块与 业务无关这一目的。
(三) 实现本发明计费方法的第三种具体实施方式如下: 在此种实施方式中, 可通过如下方式实现本发明第二种具体实施方 式中建立业务标识、 业务计费类型、 以及选择业务计费属性标识的对应 关系:
建立业务标识与业务计费类别的对应关系, 和建立业务计费类别、 业务计费类型以及选择业务计费属性标识的对应关系。
其中, 业务标识与业务计费类别的对应关系, 和业务计费类别、 业 务计费类型、 以及选择业务计费属性标识的对应关系分别以表的形式记 录;
业务标识与业务计费类别的对应关系表包含业务标识、 业务计费类 别以及折扣信息的对应关系; 其中, 折扣信息包括周期性折扣、 使用量 折扣以及与折扣相关的信息。
业务计费类别、 业务计费类型与选择业务计费属性标识的对应关系 表包括: 业务计费类别、 业务计费类型、 选择业务计费属性标识、 计费 规则、 以及辅助计费规则的对应关系; 其中, 辅助计费规则包括使用量 的最小计费标准、 使用量圓整标准等。
为了便于描述, 我们称业务标识与业务计费类别的对应关系表为表
T; 业务计费类别、 业务计费类型以及选择业务计费属性标识的对应关 系表为表 A; 选择业务计费属性标识与业务计费属性应包含字段名称的 对应关系表为表 S; 业务计费属性与计费规则的对应关系表为表 P; 其中, 表 P是表 S的子表, 通过分析现有业务的业务计费属性应包 含的字段数, 在表 S中定义足够多的列数, 表 S中与业务计费属性字段 名称相关的列数应大于任何一个现有业务的业务计费属性包含的字段 数, 表 S中的列数也应该大于将来开展业务的业务计费属性所包含的字 段数, 表 S中的列数同样应该大于修改原有业务的业务计费属性后的业 务计费属性应包含的字段数。 如此定义表 S中的列数, 以使得当原有业 务的业务计费属性需要增加字段时, 只需要在表 S中查询到需要增加该 原有业务的业务计费属性的记录, 并在此记录中增加一列信息即可; 例 如,对于 IP电话拨叫业务,原来是以主叫号码和被叫号码为业务计费属 性进行计费的,如果需要将 IP电话拨叫业务的业务计费属性修改为主叫 号码、 被叫号码和转接号码, 则在原有的记录中增加一列转接号码信息 即可, 而不需要修改表 S的结构; 从而, 当需要开展新的业务时, 只需 要在表 S中新增一条相应的记录, 该记录包括新开展业务的业务计费属 性应包含的字段名称, 此记录的选择业务计费属性标识字段的值与表 A 中相关记录所包含的选择业务计费属性标识的值相对应。
表 S中的业务计费属性应包含字段名称的相关字段与表 P的业务计 费属性相关字段的对应关系如附图 2所示。
当需要修改表 S中的记录或在表 S中增加记录时, 需要将表 P中的 记录做相应的调整, 其调整方法与在表 S中增加记录、 修改原有记录中 应包含字段数量的方法相同。 如果需要修改具体某业务的计费规则, 也 可通过在表 P中做相应修改来实现; 例如, 业务计费属性为主叫号码、 被叫号码的业务, 可根据不同主叫号码和被叫号码对应不同的计费规 则,例如,主叫号码、被叫号码分别为 010、 021,对应的计费规则为 IPP— A; 主叫号码、 被叫号码分别为 010、 022, 对应的计费规则为 IPP_B; 主叫 号码、 被叫号码分别为 021、 0317, 对应的计费规则为 IPP— C; 也可根 据需要将主叫号码、被叫号码分别为 010, 022的计费规则修改为 IPP—A, 同样, 可根据需要将所有的主叫号码、 被叫号码所对应的计费规则都修 改为 IPP_A。
在本发明中, 业务侧负责建立业务使用信息表, 业务使用信息表记 录与用户发生业务相关的信息, 该相关的信息中至少包括业务计费属 性。
当原有的业务计费属性需要修改或者需要根据新开展的业务增加业 务计费属性时, 业务使用信息表根据需要修改或增加的业务计费属性信 息做相应的调整。
在建立业务使用信息表时, 可以根据不同业务计费属性信息建立不 同业务使用信息表, 将具有不同业务计费属性的待计费业务的相关信息 存放在相应的业务使用信息表中; 也可以只建立一个业务使用信息表, 将具有不同业务计费属性的待计费业务的相关信息都存放在一个业务 使用信息表中。
在本发明中, 优选根据不同业务计费属性信息建立不同业务属性信 息表, 采用此种方式会使业务使用信息表中的内容清晰、 易于管理。
下面结合附图 3对第三种具体实施方式做进一步说明。
假定用户需要申请使用 IP电话业务, 该 IP电话业务对应的业务计费类 别有 IP1和 IP2, 假定用户选择了业务计费类别为 IP1的 IP电话业务, 当用户进行开户时, 业务侧为用户生成一个用户标识 USER— A , 为 USER_A要使用的业务计费类别为 IP1的 IP电话业务生成一个业务标识 SERVICE— IP1 , 业务标识 SERVICE— IP1对应 USER— A所申请使用的业 务计费类别为 IP1的 IP电话业务, 并将 USER— A注册的相关信息存储 在表 T中, 表 T中包含业务标识 SERVICE— IP 1、 用户标识 USER_A、 业务计费类别 IP1和折扣信息等;折扣信息包括用户享受的周期性折扣、 使用量折扣及与折扣相关信息;
在步骤 300中, 当用户 USER— A使用业务计费类别为 IP1的 IP电 话业务时, 由业务侧根据 USER_A使用 IP电话业务的情况, 产生一个 使用量事件; 该事件的标识为 EVENT— A, 用户 USER— A使用业务计费 类别为 IP1 的 IP电话业务的相关信息由该事件记录; 然后, 执行步骤 310;
其中, 该使用量事件的类型为业务计费类型;
用户 USER_A所使用的业务计费类别为 IP1的 IP电话业务的事件 类型为使用量类型;
该事件中包含用户 USER— A的使用业务计费类别为 IP1的 IP电话 业务的信息, 例如, 开始使用时间: 2001-01-01 00: 00: 00、 结束使 用时间: 2001-01-01 01 : 00 : 00、 用户标识 USER— A、 业务标识 SERVICE— IP1、 以及业务使用信息表的表名;
业务侧将事件中包含的业务信息按照事件所提供的业务使用信息表 中的要求, 向业务使用信息表中写入相关的业务信息, 如主叫号码为 010、 被叫号码为 021等;
在步骤 310中,从所述事件中获取业务标识 SERVICE— IP1后,执行 步骤 320, 根据业务标识 SERVICE_IP1 , 从表 T中获取与该业务标识相 对应的折扣信息、 业务计费类别 IP1; 然后, 执行步骤 330, 根据业务计 费类别 IP1和事件类型为使用量类型, 从表 A中查找 IP1和使用量类型 对应的记录中是否包含计费规则, 如果包含计费规则, 则执行步骤 340, 获取计费规则和辅助计费规则, 然后执行步骤 350;
在步骤 330中, 如果不包含计费规则, 则执行步骤 331, 获取记录 中的选择业务计费属性标识和辅助计费规则, 然后执行步骤 332, 根据 获取的选择业务计费属性标识, 在表 S中查找对应的记录, 获取记录中 业务计费属性包含的字段名称, 如主叫号码和被叫号码; 根据获取的业 务计费属性包含的字段名称, 在事件提供的业务使用信息表中查找业务 计费属性为 010、 021; 然后执行步骤 333 ,根据业务计费属性 010、 021 , 从表 P中获取 010、 021所对应的计费规则, 然后执行步骤 350;
其中,辅助计费规则为使用量的最小计费标准、使用量圆整标准等; 在步骤 350中, 根据待计费业务的相关信息, 如开始使用时间、 结 束使用时间、 折扣信息、 辅助计费规则和计费规则中包含的待计费业务 对应的费率, 对待计费业务进行计费, 从而实现计费系统与业务无关的 目的。
如附图 4所示, 本发明还提供一种基于实现上述计费方法的计费系 统。
在图 4中, 400是本发明所提供的计费系统, 该计费系统 400包括: 获取计费规则模块 410和计费处理模块 420;
获取计费规则模块 410根据待计费业务的业务属性获取待计费业务 的计费规则、 折扣和辅助计费规则; 将待计费业务的计费规则、 折扣信 息和辅助计费规则传输至计费处理模块 420;
计费处理模块 420根据从获取计费规则模块 410传输来的待计费业 务的计费规则、折扣信息、辅助计费规则, 为待计费业务进行计费处理。 获取计费规则模块 410包括: 获取业务计费类别子模块 430、 判别 子模块 440、获取业务计费属性子模块 450、和获取计费规则子模块 460; 其中, 获取业务计费类别子模块 430根据待计费业务的业务属性中 的业务标识, 获取待计费业务对应的业务计费类别及折扣信息, 将获取 的折扣信息传输至计费处理模块 420, 将获取的业务计费类别传输至判 别子模块 440;
判别子模块 440根据待计费业务的业务属性承载的业务计费类型和 从获取业务计费类别子模块 430传输来的业务计费类别, 判断业务计费 类别、 业务计费类型以及选择业务计费属性标识对应关系中是否包含待 计费业务的业务计费类型和业务计费类别对应的计费规则, 如果包含计 费规则, 将 "不需要获取选择业务计费属性" 标识传输至获取计费规则 子模块 460; 如果不包含计费规则, 将 "需要获取待计费业务的业务计 费属性" 传输至获取业务计费属性子模块 450;
获取业务计费属性子模块 450当接收到判别子模块 440传输来的 "需 要获取待计费业务的业务计费属性" 时, 从业务计费类别、 业务计费类 型以及选择业务计费属性标识对应关系中, 获取所述待计费业务对应的 选择业务计费属性标识和辅助计费规则; 将辅助计费规则传输至计费处 理模块 420; 根据选择业务计费属性标识获取业务计费属性应包含的字 段, 根据业务计费属性应包含的字段, 在待计费业务属性中查找对应的 业务计费属性 , 将业务计费属性传输至获取业务计费规则子模块 460; 当获取计费规则子模块 460接收到判别子模块 440传输来的 "不需 要获取选择业务计费属性" 标识时, 从业务计费类别、 业务计费类型以 及选择业务计费属性标识对应关系中获取所述待计费业务对应的计费 规则和辅助计费规则, 并将其传输至计费处理模块 420; 当获取计费规 则子模块 460接收到获取业务计费属性子模块 450传输来的业务计费属 性时, 根据业务计费属性从业务计费属性与计费规则的对应关系中获取 其对应的计费规则, 并将其传输至计费处理模块 420;
计费处理模块 420根据传输来的计费规则、 折扣信息、 辅助计费规 则对待计费业务进行计费。
以上所述仅为本发明的较佳实施例而已, 并不用以限制本发明, 凡 在本发明的精神和原则之内, 所作的任何修改、 等同替换、 改进等, 均 应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种实现计费的方法, 其特征在于, 该方法包括:
a、建立待计费业务的业务属性与该待计费业务的计费规则的对应关 系;
b、 当需要对待计费业务进行计费时,获取所述待计费业务的业务属 性;
c、根据业务属性与计费规则的对应关系, 由所述待计费业务的业务 属性获取所述该待计费业务的计费规则;
d、根据获取的待计费业务的计费规则,统一对所述待计费业务进行 计费处理。
2、如权利要求 1所述的方法, 其特征在于, 所述业务属性至少包括 业务标识和业务计费类型。
3、 如权利要求 2所述的方法, 其特征在于, 步骤 a包括: al、 建立业务标识、 业务计费类型与业务计费属性应包含字段名称 的对应关系;
a2、 建立业务计费属性与所述计费规则的对应关系。
4、 如权利要求 3所述的方法, 其特征在于, 步骤 c包括: cl、 根据业务标识、 业务计费类型与业务计费属性应包含字段名称 的对应关系, 由待计费业务的业务标识和业务计费类型, 获取所述待计 费业务的业务计费属性应包含字段名称;
c2、 根据所述待计费业务的业务计费属性应包含字段名称, 确定所 述待计费业务的业务计费属性;
c3、 根据业务计费属性与计费规则的对应关系, 由所述待计费业务 的业务计费属性获取所述待计费业务的计费规则。
5、 如权利要求 3所述的方法, 其特征在于, 步骤 al包括: al l ,建立业务标识、 业务计费类型以及选择业务计费属性标识的对 应关系;
al2、建立选择业务计费属性标识与所述业务计费属性应包含字段名 称的对应关系。
6、 如权利要求 5所述的方法, 其特征在于, 步骤 c包括: c4、 根据业务标识、 业务计费类型以及选择业务计费属性标识的对 应关系, 由所述待计费业务的业务标识和业务计费类型获取所述待计费 业务的选择业务计费属性标识;
c5、 根据所述待计费业务的选择业务计费属性标识, 获取所述待计 费业务的业务计费属性应包含字段名称;
c6、 根据选择业务计费属性标识与业务计费属性应包含字段名称的 对应关系, 由所述待计费业务的业务计费属性应包含字段名称确定所述 待计费业务的业务计费属性;
c7、 根据业务计费属性与计费规则的对应关系, 由所述待计费业务 的业务计费属性获取所述待计费业务的计费规则。
7、 如权利要求 5所述的方法, 其特征在于, 步骤 al l包括: al l K 建立业务标识与业务计费类别的对应关系;
al l2、 建立业务计费类别、 业务计费类型以及选择业务计费属性标 识的对应关系。
8、 如权利要求 7所述的方法, 其特征在于, 所述业务标识与业务计 费类别的对应关系包括: 所述业务标识、 业务计费类别以及折扣信息的 对应关系;
其中, 折扣信息包括周期性折扣及使用量折扣信息。
9、如权利要求 7或 8所述的方法,其特征在于,所述业务计费类别、 业务计费类型以及选择业务计费属性标识的对应关系包括:
业务计费类别、 业务计费类型、 选择业务计费属性标识、 计费规则 以及辅助计费规则的对应关系;
其中, 所述的辅助计费规则包括使用量的最小计费标准、 使用量圆 整标准。
10、如权利要求 5所述的方法, 其特征在于, 步骤 a2所述业务计费 属性与计费规则的对应关系以表的形式记录; 步骤 al2所述选择业务计 费属性标识与业务计费属性应包含的字段名称的对应关系以表的形式 记录。
11、如权利要求 10所述的方法,其特征在于所述的业务计费属性与 计费规则的对应关系表是选择业务计费属性标识与业务计费属性应包 含的字段名称的对应关系表的子表, 且通过业务计费属性标识相互关 联;
所述的业务计费属性与计费规则的对应关系表中的与业务计费属性 相关字段一一对应于选择业务计费属性标识与业务计费属性应包含的 字段名称的对应关系表中的业务计费属性应包含的字段名称的相关字 段。
12、 如权利要求 11所述的方法, 其特征在于, 所述业务计费属性与 计费规则的对应关系表和所述的选择业务计费属性标识与业务计费属 性应包含的字段名称的对应关系表的字段数分别大于任意业务计费属 性的字段数。
13、 如权利要求 10所述的方法, 其特征在于, 该方法进一步包括: 当业务计费属性应包含的字段名称需要增加时, 所述的业务计费属 性与计费规则的对应关系表和所述的选择业务计费属性标识与业务计 费属性应包含的字段名称的对应关系表在相应的记录中增加列信息。
14、 如权利要求 7所述的方法, 其特征在于, 步骤 c包括: c8、 根据业务标识与业务计费类别的对应关系, 由所述待计费业务 的业务标识获取所述待计费业务的业务计费类别和折扣;
c9、 根据所述的业务计费类别、 业务计费类型与选择业务计费属性 标识的对应关系中是否包括所述待计费业务的业务计费类别、 业务计费 类型对应的计费规则, 判断是否需要获取业务计费属性, 如果是, 则执 行步骤 c91 , 否则执行步骤 c95;
c91、根据业务计费类别、业务计费类型以及选择业务计费属性标识 的对应关系, 获取所述的业务计费类别、 业务计费类型对应的选择业务 计费属性标识和辅助计费规则;
c92、根据所述待计费业务的选择业务计费属性标识获取所述待计费 业务的业务计费属性应包含的字段名称;
c93、根据所述待计费业务的业务计费属性应包含的字段名称获取所 述待计费业务的业务计费属性;
c94、根据所述待计费业务的业务计费属性获取所述待计费业务的计 费规则;
c95、获取所述的业务计费类别、业务计费类型对应的计费规则和辅 助计费规则。
15、 如权利要求 14所述的方法, 其特征在于, 步骤 d包括: 根据所述计费规则、 折扣信息和辅助计费规则对所述待计费业务进 行计费处理。
16、 一种基于实现上述计费方法的计费系统, 其特征在于, 该系统 包括:
获取计费规则模块: 根据待计费业务的业务属性获取待计费业务对 应的计费规则, 将该计费规则传输至计费处理模块; 计费处理模块:根据传输来的计费规则对待计费业务进行计费处理。
17、如权利要求 15所述的计费系统, 其特征在于, 所述获取计费规 则模块包括:
获取业务计费类别子模块: 用于根据待计费业务的业务属性中的业 务标识获取所述待计费业务对应的折扣和业务计费类别; 将所述折扣输 出到所述计费处理模块; 将所述的业务计费类别输出到判别子模块; 判别子模块: 用于根据接收到的业务计费类别, 由计费类别、 业务 计费类型以及选择业务计费属性标识的对应关系中是否包含待计费业 务对应的计费规则判断是否需要获取业务计费属性; 如果不需要, 则通 知获取业务计费规则子模块不需要获取待计费业务的业务计费属性, 如 果需要, 则通知获取业务计费属性子模块需要获取待计费业务的业务计 费属性;
获取业务计费属性子模块: 当接收到需要获取待计费业务的业务计 费属性通知时, 从业务计费类别、 业务计费类型以及选择业务计费属性 标识的对应关系中, 获取待计费业务对应的选择业务计费属性标识和辅 助计费规则; 根据选择业务计费属性标识获取业务计费属性应包含的字 段名称; 根据业务计费属性应包含的字段名称获取业务计费属性; 将辅 助计费规则传输至计费处理模块; 将业务计费属性传输至获取计费规则 子模块;
获取业务计费规则子模块: 当接收到不需要获取待计费业务的业务 计费属性通知时, 从业务计费类别、 业务计费类型以及选择业务计费属 性标识的对应关系中, 获取待计费业务对应的计费规则并将获取的计费 规则传输至所述计费处理模块; 当接收到业务计费属性时, 从业务计费 属性与计费规则的对应关系中获取计费规则, 将获取的计费规则传输至 所述计费处理模块。
PCT/CN2004/000884 2003-07-31 2004-07-30 Procede de mise en oeuvre de compte et systeme de compte WO2005011194A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/566,952 US7526075B2 (en) 2003-07-31 2004-07-30 Method of implementing account charging and account charging system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB031440835A CN100365980C (zh) 2003-07-31 2003-07-31 一种实现计费的方法及计费系统
CN03144083.5 2003-07-31

Publications (1)

Publication Number Publication Date
WO2005011194A1 true WO2005011194A1 (fr) 2005-02-03

Family

ID=34085335

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2004/000884 WO2005011194A1 (fr) 2003-07-31 2004-07-30 Procede de mise en oeuvre de compte et systeme de compte

Country Status (3)

Country Link
US (1) US7526075B2 (zh)
CN (1) CN100365980C (zh)
WO (1) WO2005011194A1 (zh)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1960264A (zh) * 2005-11-03 2007-05-09 华为技术有限公司 一种计费的方法和系统
US7697672B2 (en) * 2005-11-29 2010-04-13 Accenture Global Services Gmbh Configurable rating system for a telecommunications service provider
US7831027B2 (en) * 2006-01-25 2010-11-09 Accenture Global Services Limited Configurable charging system for a telecommunications service provider
CN101277201B (zh) * 2007-03-29 2011-03-16 中兴通讯股份有限公司 一种综合计费的实现方法及其装置
CN101562529B (zh) * 2008-04-14 2011-06-01 华为技术有限公司 一种计费处理的方法及装置
US9118491B2 (en) * 2010-06-30 2015-08-25 Alcatel Lucent Return of multiple results in rule generation
CN102223616B (zh) * 2011-07-11 2015-05-27 华为软件技术有限公司 一种计费方法及装置
CN102348184A (zh) * 2011-07-13 2012-02-08 南京中兴软创科技股份有限公司 计费系统中使用分区图处理计费信息、求解计费属性的方法
CN103490909B (zh) * 2012-06-13 2018-03-27 中兴通讯股份有限公司 计费处理方法及装置
US10115092B1 (en) 2016-03-04 2018-10-30 Sprint Communications Company L.P. Service composition in a mobile communication device application framework
WO2017193303A1 (zh) * 2016-05-11 2017-11-16 华为技术有限公司 一种通信计费方法
CN109951302A (zh) * 2019-02-26 2019-06-28 启迪云计算有限公司 一种基于数据字典自定义产品的云计算计费系统及方法
CN113570311A (zh) * 2021-08-06 2021-10-29 上海中通吉网络技术有限公司 快递国际业务的费用清洗方法及设备

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1373586A (zh) * 2001-03-01 2002-10-09 深圳市中兴通讯股份有限公司 通用网间计费方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5185785A (en) * 1991-10-31 1993-02-09 At&T Bell Laboratories Method and apparatus for recording and rating telecommunication transactions made over a communication network
SG43099A1 (en) * 1994-03-02 1997-10-17 British Telecomm Charging for usage of a telecommunications network
US6011837A (en) * 1998-06-22 2000-01-04 Bellsouth Intellectual Property Corporation Marketing control program
US20010056362A1 (en) * 1998-07-29 2001-12-27 Mike Hanagan Modular, convergent customer care and billing system
GB9927597D0 (en) * 1999-11-22 2000-01-19 Nokia Networks Oy Improving charging efficiency
JP3584838B2 (ja) * 2000-02-22 2004-11-04 日本電気株式会社 パケット監視システム、パケット監視方法及びそのプログラムを記録した記録媒体
US20020068545A1 (en) * 2000-11-06 2002-06-06 Johnson Oyama Method and apparatus for coordinating charging for services provided in a multimedia session
CN1395391A (zh) * 2001-07-09 2003-02-05 深圳市中兴通讯股份有限公司 一种宽带接入网络计费方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1373586A (zh) * 2001-03-01 2002-10-09 深圳市中兴通讯股份有限公司 通用网间计费方法

Also Published As

Publication number Publication date
US7526075B2 (en) 2009-04-28
US20070274481A1 (en) 2007-11-29
CN1581782A (zh) 2005-02-16
CN100365980C (zh) 2008-01-30

Similar Documents

Publication Publication Date Title
WO2005011194A1 (fr) Procede de mise en oeuvre de compte et systeme de compte
WO2020119325A1 (zh) 计费处理方法及装置、存储介质和电子装置
US20020087353A1 (en) Method of connecting calls between a business card transmitter and a business card receiver through the medium of a web business card sent by the business card transmitter and system for the same
US20020026489A1 (en) Method of transferring message received and stored in the absence of the user
JP2002345030A (ja) ウェブサイトアクセスサービス提供システム
US20030185362A1 (en) Communication system and communication service method through internet call intermediation
WO2007062545A1 (fr) Procede pour l'acces du terminal d'appelant a un systeme de service prepaye
US8019062B2 (en) Method and system for transferring an administrator and associated charges during a multi-way call
JP5505297B2 (ja) コールバックシステム、発信端末、電話中継サーバ、コールバック方法、及びコールバックプログラム
KR100700706B1 (ko) 통신 시스템에서 수신자 통화료 부담 서비스를 제공하는방법 및 상기 방법을 채용한 통신 시스템
JP2003058565A (ja) 情報検索システム、情報検索サーバ、情報提供方法及びプログラム
KR100335291B1 (ko) 인터넷 전화를 이용한 공중전화망의 착신자 요금 부담서비스 제공 방법 및 장치
KR100706333B1 (ko) 착신자 통신료 부담 서비스에 따른 데이터 통신료 처리방법 및 시스템
JP2003348266A (ja) 通信システム
JPH10285304A (ja) 電話システム、電話回線網のセンタ装置、端末装置及び通話料金分計方法
KR20000012226A (ko) 인터넷을 이용한 유료전화 서비스 제공방법
JP2002142023A (ja) サーバシステム及び通信データ送出方法
KR100683287B1 (ko) 제 3자 과금 콜렉트콜 전화 서비스 제공 방법
JP3099282U (ja) 携帯電話機に係る課金管理制御装置
KR100838156B1 (ko) 인터넷폰 서비스 제공방법
JP2982918B2 (ja) 高度通信サービス方式
JP2003318993A (ja) インターネットコール仲介を利用した通話システム及び通話サービス方法
JP4275575B2 (ja) 電話交換システム及びサーバ並びにゲートウェイ
JP2011172183A (ja) 電話番号案内自動接続システム、番号案内自動接続装置、加入者サーバおよび課金方法
KR20110087903A (ko) 타인 단말 상에서 메시지를 이용한 호 연결 시스템 및 이를 이용한 과금 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
WWE Wipo information: entry into national phase

Ref document number: 10566952

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 10566952

Country of ref document: US