WO2012167702A1 - 一种计费重批的方法及装置 - Google Patents

一种计费重批的方法及装置 Download PDF

Info

Publication number
WO2012167702A1
WO2012167702A1 PCT/CN2012/076200 CN2012076200W WO2012167702A1 WO 2012167702 A1 WO2012167702 A1 WO 2012167702A1 CN 2012076200 W CN2012076200 W CN 2012076200W WO 2012167702 A1 WO2012167702 A1 WO 2012167702A1
Authority
WO
WIPO (PCT)
Prior art keywords
batch
group
heavy
bill
bills
Prior art date
Application number
PCT/CN2012/076200
Other languages
English (en)
French (fr)
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 WO2012167702A1 publication Critical patent/WO2012167702A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1428—Invoice generation, e.g. customization, lay-out, database processing, algorithms for calculating the bill or formatting invoices as WWW pages
    • 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/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/43—Billing software details
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/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

Definitions

  • the invention relates to a method and a device for re-granting a bill.
  • the application is submitted to the Chinese Patent Office on June 8, 201, and the application number is 201 1 10152502.2, and the invention name is "a method and device for re-batching".
  • Priority of Chinese Patent Application the entire contents of which is incorporated herein by reference.
  • the present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for charging re-batch. Background technique
  • the billing method of the mobile phone service the operator gives a variety of billing packages for different user groups. For example, for the user group with more voice services, the calling party has 1 point/minute, the called party is free, and the SMS is 1.5 corner/bar billing package. For the customer group with more SMS service, the caller is given 2.5 angle/ Minutes, called 1 pt / min, SMS 0.5 pt / strip billing package.
  • billing errors may occur due to various reasons such as the missing number of the service number and the configuration error of the resource data.
  • the bill of the billing error is re-granted.
  • the re-approval is to re-approve the price, correct the bill for billing errors through re-approval operation, and re-approve the bill as a list of bills that need to be re-approved.
  • the re-batch method in the prior art has the following steps: 1. According to the business time, the business type is selected to re-submit the bill; 2. The selected bills that need to be re-granted are rolled back, and the rollback includes all the influential Data, such as: one or more of detailed bills, balances, free resources, and cumulative amounts; 3. Re-pricing in order of bills, that is, re-rating each business.
  • the re-approval method is to re-grant the bills first. According to different business types, they are selected into different heavy-duty bill files and re-approved according to the business type. This will result in a heavy re-approval of the business that will occur after the business type is different. For example, the heavy-duty CDRs of the voice service type are ranked first in the re-approval, followed by the heavy-duty CDRs of the SMS service. If the CDRs happening after the priority re-approval, the SMS generates free resources. In the case of re-approval, the short message service that has been generated before the voice bill occurs will also be enjoyed by the free SMS resource, and will be processed freely when the batch is re-submitted, resulting in a billing error during re-approval.
  • the multi-user package is a plurality of users under a paid account, such as a group business package and a family business package.
  • the service fee of the user in the multi-user package is deducted from the payment account before the total amount of the pre-paid account is used. After the total amount of the pre-paid in the payment account is used, the user pays the amount.
  • Multiple users of the group business or home business may be distributed on different network nodes. For example, during the charging error time period, multiple users under the same group service have services on multiple nodes, according to the existing The technology, in the case of re-approval, is re-approved according to the service node. If the network node where the user who has the business after the re-approval is re-granted in priority, the user of the network node that happens to be re-approved is heavy. After the re-grant of the batch of bills, the total cost of the group's business is used up, and the re-generated business expenses are paid by the employees themselves. This will cause the users who first have business to be paid for by the network nodes that are re-approved afterwards. This re-batch method of the prior art causes a billing error in re-approval. Summary of the invention
  • the embodiment of the invention provides a method and a device for re-granting a batch, by selecting all the heavy batches of the same paying account into the same heavy batch of bills, and re-approving according to the chronological order, The accuracy of the heavy approval.
  • a method for billing re-batch comprising:
  • the heavy CDRs of the same first payment account within the time when the charging error occurs are selected into the same heavy CDR group, and the first payment account refers to being charged at the time of payment.
  • Priority debit account
  • the heavy batch of bills in the re-approved bill group is re-approved according to the order of the business occurrence time, and after the re-approval of all the heavy-duty bills in the re-approved bill group, the re-approved bill group
  • the re-granted bills are submitted to the accounting system.
  • a device for re-batch charging comprising:
  • the pick unit according to the first paying account, will be the same time during the billing error
  • the heavy bills of the first paying account are selected into the same heavy bill group, and the first paying account refers to the account that is preferentially deducted when paying;
  • the re-approval unit is used to re-approve the heavy-duty CDRs in the re-approved CDR group according to the order of the business occurrence time, and after all the heavy-duty bills in the re-approved CDR group are completed in batches, The re-granted bills in the heavy-duty bill group are uniformly submitted to the accounting system.
  • the heavy CDRs in the charging error occurrence time are selected into different heavy CDR groups according to different first payment accounts, and the first payment account is preferentially deducted at the time of payment.
  • the re-granted bills in the bill group are submitted to the accounting system.
  • the embodiment of the present invention ensures that the accuracy of the charging is ensured by selecting all the heavy CDRs under the same payment account into the same heavy batch CDR group and re-granting them in chronological order.
  • FIG. 1 is a schematic diagram of an embodiment of a method for charging re-granting according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a first embodiment of an apparatus for charging a heavy batch according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a second embodiment of a device for charging a heavy batch according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a re-batch device of a device for charging a heavy batch according to an embodiment of the present invention. detailed description
  • a first embodiment of a method for charging re-batch includes: 101. Select, according to the first payment account, the heavy CDRs of the same first payment account within the time period of the charging error to be selected into the same heavy CDR group;
  • the re-approval bills are bills that need to be re-approved, and the re-approval bills correspond to the services performed by the user.
  • the first payment account is a multi-user shared account, such as a group account, a family account, or a single-user account, such as one account for one user;
  • the single-user account in the embodiment of the present invention refers to an account of a single user who has generated a plurality of services within a charging error occurrence time.
  • the multi-user shared account is that a plurality of users share one account during the charging error occurrence time.
  • the fee generated by the user under the shared account is deducted from the shared account before the cost of the shared account is deducted.
  • the user under the shared account is generated.
  • the business fee is deducted from the user's personal payment account, but refers to the service of the shared account deduction.
  • the user's personal account under the shared account can only be used as a backup payment account, and cannot be used as the first payment account, such as the group.
  • the expenses incurred by the employees of the group are deducted from the employee's personal account after the expenses under the group account are used up. However, in this case, the group account is still the first paid account, and the employee account is used as the employee account. Alternate payment account, but for the expenses incurred by the employee's short message service, the employee's payment account is counted as the first payment account;
  • the selection error is caused by the same user.
  • the heavy CDRs deducted by the user under the shared account are selected into the re-granting CDR group of the shared account, and in the remaining CDRs, the user is charged in the single-user account.
  • the heavy CDRs in the batch group will be rolled back uniformly, and then the above-mentioned picking process will be repeated, and the re-granting will be carried out again to ensure the accuracy of the re-batch.
  • the heavy batches in different re-batch groups are re-batched in parallel, because the heavy-duty bills under different paying accounts are not associated, and parallel re-batch can increase the speed of re-batch.
  • the heavy CDRs of the same first payment account are selected into the same heavy batch CDR group according to the difference of the first payment account, and the heavy CDRs in the heavy CDR group are followed.
  • the method further includes adding an CDR field for the re-granting CDR, and adding the identifier to the re-granting CDR group after selecting the heavy CDR to the heavy CDR group.
  • the identifier of the heavy batch of bills is used as the first bill field added to the heavy batch bill, and the heavy bills are numbered in the reorder batch group according to the order of occurrence of the business, and the heavy bills are The number of the re-invoice in the group is used as the second bill field added to the heavy-duty bill.
  • the method further includes selecting the re-approved CDRs according to the chronological order of the network node and the re-granting CDRs of the user.
  • the re-granting of the re-granted bills generated by the first network node may be faster, and the heavy-duty bills of the second network node before the service occurs. If it has not been completed in batches, it has already begun to re-approve the next batch of CDRs generated at the first network node, resulting in a re-batch error.
  • the micro-batch group number can also be numbered as the third bill field added to the bills in the micro-burst group, in the micro-batch
  • the order of the re-granting bills may be further sequenced as the fourth bill field added to the heavy bill, and when the heavy bills in the micro-burst group are re-granted.
  • the second micro-grant batch group will be re-approved after the batch is completed, and the second vouchers group will be re-granted.
  • the bill type field of the service type must be added to ensure that the different businesses should be accurately changed in the re-approval. Cost, so when re-approving, it is determined according to the type of business, re-approving different variable expenses corresponding to different businesses, and re-granting the re-granted bills according to different variable expenses, so that each batch after re-approval can be guaranteed The accuracy of the billing of the business type.
  • mobile phone billing system 2011-1-1 00:00:00 to 2011-1- 1 01 :00:00 billing error requires a 0.5-point surcharge for each business for a fee-paying service.
  • 00: 00: 05 initiate SMS business, pay 0.5 pt, 00: 03: 05 to initiate SMS business, free, 00: 04: 00 to initiate GPRS service 600 seconds, pay 1 cent.
  • User 12000000002 initiated voice service for 121 seconds at 2011-1-1 00: 01:02, paying 3 horns.
  • Users 12800000000 and 12900000002 belong to the same group, but they are deployed in two network nodes: CBS101 and CBS102.
  • the Yuantian Group pays a total of 1000 ⁇ , and Yuantian Group has paid 998 at 2011-1-1 00:00:00.
  • User 12800000000 initiates a call at 00:01:00 for 600 seconds, and Yuantian Group pays for 10 horns;
  • 12900000002 initiates a call at 00:01:10 for 630 seconds, pays 10 cents by Yuantian Group, pays 1 cent for itself; user 12900000002 initiates a call at 00: 14:10, pays for 11 cents;
  • SMS service bill format:
  • call-type call type
  • 00-caller 01-called
  • Charging-number billing party number; Other-party, party number;
  • Start-time service start time
  • send-time send time
  • end-time at the end of the service Duration
  • duration unit seconds
  • traffic traffic, unit bytes
  • fee cost, unit angle.
  • the group's business re-bill format adds a field share-fee to the end of the heavy-duty bill for personal business. Where fee represents the payment result of the own account; share-fee represents the payment result of the group.
  • the re-approval method is as follows: According to the time when the error occurred, 2011-1-1 00:00:00 to 2011-1-1 01:00:00, the re-approved bills are selected, and the selected re-issued bills are:
  • the same heavy-duty bill group selected by the heavy-duty bill under the same paying account is selected as:
  • the Yuantian Group After selecting the re-approved bills from the above-mentioned Yuantian Group account to the Yuantian Group's re-approved bill group, it will further select the heavy-duty bills in the re-approved bill group of the Yuantian Group into the micro-recommended bill group. Because the two users 12800000000 and 12900000002 under the Yuantian Group are deployed on the CBS101 and CBS102 network nodes respectively, the Yuantian Group will re-approve the bill group according to the order of the network node and the bill business time. The re-approved bills are selected in sequence to different micro-burst batches; when selecting the heavy-duty bills under the Yuantian Group account, the re-granting bills are added to the bills field, which will be re-granted.
  • the identifier is added to the re-approved bill group, and the identifier of the re-approved bill group is used as the first bill field added to the heavy-duty bill, and the re-approved bill group is
  • the number of the re-issued bills is numbered according to the order in which the services occur, and the number of the re-invoices in the re-invoice group is used as the second bill field added to the heavy-duty bill, and the added first field indicates the weight
  • the order number of the batch of bills in the re-approved bill group, 0 means the first item
  • 999999 means the last item
  • the micro-batch batch number is used as the third field.
  • the heavy-duty bills are numbered in chronological order. 0 means the first one, 999999 means the last one, and the last one added.
  • the field is the business type.
  • the heavy CDRs in the micro heavy batch list in the re-approved CDR group of the Yuantian Group are respectively; the first micro heavy batch CDR group is the heavy CDR of the user at the CBS101 network node:
  • the second micro-recommended CDR group is the heavy CDR of the CBS102 network node user:
  • the third micro-recommended CDR group is the heavy CDR of the user at the CBS101 network node:
  • the first digit indicates the number of the re-invoice group
  • the second digit indicates the order of the re-invoice in the re-invoice group.
  • No. 0 means the first one
  • 999999 means the last one
  • the third digit indicates the service type, voice, SMS or GPRS.
  • the heavy CDRs in the first micro heavy batch list are:
  • the heavy CDRs in the second micro heavy batch list are:
  • the heavy CDRs in the third micro heavy batch list are:
  • the re-granting of the re-grants of the three micro-re-scheduled CDRs in the respective CDR groups is completed as a transaction. Only after the first micro-grant batches are re-approved, will the The second micro-recommended CDR group is re-approved, followed by the third micro-grant batch CDR group, and the transaction will be terminated only after the heavy CDRs in the three micro-grant batches are re-approved. Submit in a unified manner. If there is an error in the re-approval of a heavy batch of bills during the re-approval process, the heavy-duty bills in the three micro-burst batches will be rolled back uniformly, and then the above-mentioned picking and sorting process will be repeated. , re-grant again to ensure the accuracy of the re-batch.
  • the reordered bills in the user's 12000000000 re-bill group are:
  • the re-granting of the heavy CDRs in the first CDR group of the second CDR file is also completed as a transaction, and only all the heavy CDRs in the first CDR group are re-approved. Submit, if there is an error in the re-approval of the re-approval, all the re-grants in the second re-bill group will be rolled back uniformly, and then repeat the above-mentioned picking process again. Re-approval to ensure the accuracy of re-batch.
  • the heavy batches of users of different nodes under the Yuantian Group are divided into the same heavy batch of bills, and the heavy batch of one user's multiple services is divided into one heavy batch of bills.
  • the re-approved bills are re-approved according to the time of the business occurrence, and in the prior art, the re-approved bills are selected into different bill files according to the service type or different nodes.
  • the CBS101 node is not re-approved in the same group, so that the user on the CBS102 node initiates the service before the user on the CBS101 node, but the personal payment situation does not occur.
  • the apparatus for charging re-batch in the embodiment of the present invention includes:
  • the picking unit 201 selects, according to the first paying account, the heavy CDR of the same first paying account within the charging error occurrence time to the same heavy CDR group, wherein the first paying account is Refers to an account that is preferentially deducted at the time of payment.
  • the re-approval unit 202 is configured to re-submit the heavy-duty CDRs in the re-scheduled CDR group according to the order of the business occurrence time, and after all the heavy-duty bills in the re-approved CDR group are completed in batches, The re-granted bills in the re-scheduled bill group are uniformly submitted to the accounting system.
  • the picking unit 201 selects the heavy CDRs of the same first paying account within the time when the charging error occurs according to the difference of the first paying account, and re-approves the unit. 202 re-grants the re-granted bills according to the order in which the business occurred.
  • the embodiment of the present invention uses all the heavy batches of bills that satisfy the same first paying account to be selected into the same heavy batch of bills, in the same weight.
  • all the CDRs in the re-approved CDR group are re-granted according to the order in which the re-invoices correspond to the business occurrence time, which ensures the accuracy of the re-granting billing.
  • the charging re-batch device in the embodiment of the present invention further includes:
  • the bill field adding unit 302 is configured to add a bill field to the re-grant bill when the heavy bill is selected to the heavy bill group or/and the micro heavy bill group;
  • the bill-sending unit 302 adds the identifier to the re-bill group according to the order in which the picking is completed.
  • the single field is the identifier of the re-batch group;
  • the billing field adding unit 302 After the picking unit 301 selects the heavy batch of bills into the heavy batch of bills, the billing field adding unit 302 performs the re-approval of each heavy batch of bills according to the order of the business occurrence time. The order number is added in sequence, and the second bill field added by the billing field is a sequential number of the re-invoice in the re-bill group, and the re-batch unit is re-subscribed according to the sequence number. The order number of the bill is re-approved;
  • the bill list field adding unit 302 completes the selection according to the selection.
  • the order of the order will be the number of the batch number of the batch, and the unit of the bill will be added to the weight of the shared account.
  • the third field added by the batch is the number of the micro-batch group, and the micro-batch unit is re-granted in the order of the number of the micro-batch group.
  • the re-batch unit 303 further includes a plurality of micro-batch units 3031, the micro-batch unit
  • the serial re-submission is performed according to the time of occurrence of the corresponding service of the heavy-duty bills in the micro-burst group, and the re-grants in all the micro-batch groups are all re-approved. submit.
  • the ending unit 304 is configured to, when the re-batch unit 303 re-approves any one of the re-scheduled bills in the re-scheduled bill group, when the re-batch error occurs, the re-batch operation of the re-batch group is ended.
  • the ending unit 304 is further configured to: when the micro-batch unit 3031 re-approves any one of the re-invoices, when the re-batch error occurs, the re-batch operation of the micro-re-batch group is ended.
  • the bill field adding unit 302 adds the bill field to the heavy bill
  • the batch unit 303 or the micro-batch unit 3031 is re-batch, it is re-granted according to the order of occurrence of the re-batch service in the re-batch group or the micro-batch group, thereby ensuring the accuracy of billing after re-approval. .
  • the charging re-batch device may include multiple re-batch units, and each re-batch unit may also include a plurality of micro-batch units, which are corresponding to the method embodiments in the embodiments of the present invention for ease of understanding.
  • the application scenario introduces a charging re-batch device according to an embodiment of the present invention.
  • the apparatus for charging re-batch 40 of the embodiment of the present invention includes:
  • the re-approval unit 401 is configured to re-approve the re-granting bills of all the services under the account of the long-term group; the re-batch unit 402 is configured to re-submit the re-granting bills of the user with more than 12,000 million kinds of services; Micro-batch unit 4011, micro-batch unit 4012 and micro-batch unit
  • the micro-batch unit 4011 is configured to re-approve a heavy batch of bills in the first micro-batch batch group; the micro-batch unit 4012 is configured to re-approve the weight in the second micro-weight batch of bills
  • the micro-batch unit 4013 is used to re-batch the heavy-duty bills in the third micro-batch batch group; the micro-batch unit 4011 in the re-batch unit 401 in the re-batch, the micro-batch unit
  • the 4012 and the micro-batch unit 4013 are re-granted in the order from the micro-batch unit 4011 to the micro-batch unit 4013, and the heavy-duty bills in the second batch unit 402 are also in the order of the business occurrence time.
  • re-batch unit 401, re-batch unit 402 is parallel re-batch, improve billing The speed of re-approval.
  • This application scenario only gives a few heavy batches of bills, but in practice, there will be many heavy batches of bills, and the billing re-batch device is not limited to only two re-batch units, which can be re-approved according to the actual situation. Multiple re-batch units are activated by a single number. Of course, there may be multiple micro-batch units in the re-batch unit under the shared account.
  • the program can be stored in a computer readable storage medium.
  • the storage medium can include: ROM, RAM, disk or CD, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本发明公开了一种计费重批的方法，按照第一付费账户的不同，将计费错误发生时间内的重批话单挑选到不同的重批话单组中，所述第一付费账户是指在付费时被优先扣费的账户，对重批话单组内的重批话单，按照业务发生时间的先后重批，并在重批话单组内的所有重批话单重批完成后，将所述重批话单组内的重批后的话单统一提交给账务***。本发明实施例通过将同一付费账户下的所有重批话单挑选到同一个重批话单组中，按照时间先后顺序重批，保证了计费的准确性。本发明实施例还提供了相应的计费重批的装置。

Description

一种计费重批的方法及装. 本申请要求于 201 1 年 6 月 8 日提交中国专利局、 申请号为 201 1 10152502.2, 发明名称为 "一种计费重批的方法及装置" 的中国专利申 请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域， 具体涉及一种计费重批的方法及装置。 背景技术
手机业务的计费方式， 运营商针对不同用户群体给出了多种计费套餐。 如： 针对话音业务多的用户群体， 给出了主叫 1角 /分钟， 被叫免费， 短信 1.5 角 /条的计费套餐； 针对短信业务多的客户群体， 给出了主叫 2.5角 /分钟， 被 叫 1角 /分钟， 短信 0.5角 /条的计费套餐。
但随着通信技术的发展， 手机的业务种类先后又增加了彩信业务和手机 上网业务， 随着手机业务的增多， 手机计费套餐中多业务融合的计费套餐也 随之增多， 如： 话音业务消费满 100分钟， 赠送 10条短信； 当月总消费满 100元， 赠送 100条短信， 或者当月总消费满 100元后， 总消费打 95折等。
手机计费过程中因服务号码号段缺失， 资源数据配置错误等多种原因会 出现计费错误， 发现计费错误后， 就要对计费错误的话单进行重批。 重批就 是重新批价， 通过重批操作， 更正计费错误的话单， 重批话单为需要重新批 价的话费清单。
现有技术中的重批方法有以下几个步骤： 1、 根据业务时间， 业务类型挑 选需要重批话单； 2、 将挑选出的需要重批的话单进行回滚， 回滚包括所有有 影响的数据， 例如： 明细账单、余额、免费资源和累计量中的一项或多项； 3、 按话单顺序进行重新批价， 即对各个业务进行重新批价。
对于同一用户在计费错误时间段内发生了多种业务， 在重批时就会有与 业务相对应的多个重批话单， 按照现有技术的重批方法是先将重批话单按照 不同的业务类型挑选到不同的重批话单文件中， 按照业务类型进行重批。 这 样就会导致因业务类型不同， 后发生的业务的重批话单可能会被优先重批。 如语音业务类型的重批话单在重批时排在第一位， 接下来是短信业务的重批 话单， 如果恰巧在优先被重批的语音话单发生后， 短信产生了免费资源， 在 重批时， 在语音话单发生之前就已经产生的短信业务也会享受到该免费短信 资源， 在重批计费时就会被以免费处理， 导致重批时计费错误。
对于多用户套餐中， 所述的多用户套餐为一个付费帐号下有多个用户， 如集团业务套餐和家庭业务套餐。 所述多用户套餐中的用户的业务费用在付 费帐号下预付费总额使用完之前， 由付费帐号扣除， 付费帐号中的预付费总 额使用完后， 由用户个人支付。
集团业务或家庭业务的多个用户， 可能会分布在不同的网络节点上， 如 在计费错误时间段内， 同一集团业务下的多个用户在多个节点上都发生了业 务， 按照现有技术， 在重批时， 是按照业务节点进行重批的， 如果后发生业 务的用户所在的网络节点在重批时优先被重批， 而恰巧在优先被重批的网络 节点上的用户的重批话单重批完后， 集团业务的总费用用完， 再产生的业务 费用要员工自己支付， 这样就会导致先发生业务的用户因处在后被重批的网 络节点上， 导致自己付费， 现有技术的这种重批方法造成了重批时计费错误。 发明内容
本发明实施例提供了一种计费重批的方法及装置， 通过将同一付费账户 下的所有重批话单挑选到同一个重批话单组中， 按照时间先后顺序重批， 可 以保证计费重批的准确性。
一种计费重批的方法， 包括：
按照第一付费账户的不同， 将计费错误发生时间内的同一个第一付费账 户的重批话单挑选到同一个重批话单组中， 所述第一付费账户是指在付费时 被优先扣费的账户；
对重批话单组内的重批话单， 按照业务发生时间的先后顺序重批， 并在 重批话单组内的所有重批话单重批完成后， 将所述重批话单组内的重批后的 话单统一提交给账务***。
一种计费重批的装置， 包括：
挑单单元， 按照第一付费账户的不同， 将计费错误发生时间内的同一个 第一付费账户的重批话单挑选到同一个重批话单组中， 所述第一付费账户是 指在付费时被优先扣费的账户；
重批单元， 用于对重批话单组内的重批话单， 按照业务发生时间的先后 顺序重批， 并在重批话单组内的所有重批话单重批完成后， 将所述重批话单 组内的重批后的话单统一提交给账务***。
本发明实施例采用按照第一付费账户的不同， 将计费错误发生时间内的 重批话单挑选到不同的重批话单组中， 所述第一付费账户是指在付费时被优 先扣费的账户， 对重批话单组内的重批话单， 按照业务发生时间的先后重批， 并在重批话单组内的所有重批话单重批完成后， 将所述重批话单组内的重批 后的话单统一提交给账务***。 与现有技术相比， 本发明实施例通过将同一 付费账户下的所有重批话单挑选到同一个重批话单组中， 按照时间先后顺序 重批， 保证了计费的准确性。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作一筒单地介绍， 显而易见地， 下 面描述中的附图是本发明的一些实施例， 对于本领域普通技术人员来讲， 在 不付出创造性劳动的前提下， 还可以根据这些附图获得其他的附图。
图 1是本发明实施例计费重批的方法的实施例示意图；
图 2是本发明实施例计费重批的装置的第一实施例示意图；
图 3是本发明实施例计费重批的装置的第二实施例示意图；
图 4是本发明实施例计费重批的装置的重批装置示意图。 具体实施方式
本发明实施例提供一种计费重批的方法， 用于在对同一个付费账户下存 在多种业务进行重批时保证计费重批的准确性。 这里的同一个账户可以是单 用户账户， 也可以是共用账户， 如集团账户。 本发明实施例还提供相应的计 费重批的装置。 以下分别进行详细说明。 请参阅图 1 , 本发明实施例的计费重批的方法的第一实施例包括： 101、按照第一付费账户的不同， 将计费错误发生时间段内的同一个第一 付费账户的重批话单挑选到同一重批话单组中；
在一段时间内发生计费错误时， 就需要对错误时间段内的话单进行重新 批价， 重批话单也就是需要重新批价的话单， 重批话单与用户进行的业务相 对应。
第一付费账户为多用户共用账户， 如集团账户、 家庭账户， 也可以是单 用户账户， 如一个用户一个账户；
本发明实施例中的单用户账户是指在计费错误发生时间内发生了多种业 务的单个用户的账户， 多用户共用账户为在计费错误发生时间内多个用户共 用一个账户。 对于多用户账户下的单个用户， 在共用账户的费用未扣完前， 共用账户 下的用户产生的费用从共用账户下扣除， 当共用账户下的费用扣完后， 共用 账户下的用户所产生的业务费用从该用户的个人付费账户中扣除， 但是涉及 到共用账户下扣费的业务， 所述共用账户下的用户的个人账户只能作为备用 付费账户， 不能作为第一付费账户， 如集团负责公司员工的话音业务费用， 集团员工打电话所产生的费用在集团账户下的费用用完后， 从员工的个人账 户扣除， 但此种情况， 集团账户依然是第一付费账户， 员工账户作为备用付 费账户， 但是对于员工的短信业务产生的费用， 员工的付费账户算作第一付 费账户；
若在计费错误的时间段内， 共用账户下的用户既有共用账户作为第一付 费账户的业务发生， 又有个人单用户账户作为第一付费业务发生， 为避免因 用户相同， 造成选择错误， 优先将所述用户在共用账户下扣费的重批话单挑 选到共用账户的重批话单组内， 在剩余的话单中， 再将该用户在单用户账户 下扣费的重批话单挑选到该单用户账户下的重批话单组内。
102、 对重批话单组内的重批话单， 按照业务发生时间的先后顺序重批， 并在重批话单组内的所有重批话单重批完成后， 将所述重批话单组内的重批 后的话单统一提交给账务***； 对重批话单组内的重批话单按照业务发生时间的先后顺序重批， 重批时 是将重批话单组的重批操作作为一个事务来完成的， 若在重批到任意一条话 单时， 发生重批错误， 要结束对该重批话单组的重批操作， 所有重批话单组 中的重批话单将统一进行回滚， 再重复上述挑单过程， 再次进行重批， 以保 证重批计费的准确性。 不同重批话单组中的重批话单是并行重批的， 因为不 同付费帐号下的重批话单不相关联， 并行重批可以提高重批的速度。 本实施例中， 通过按照第一付费账号的不同， 将同一个第一付费账号的 重批话单挑选到同一个重批话单组中， 按照重批话单组内的重批话单按照业 务发生时间的先后顺序重批， 与现有技术相比， 保证了计费重批的准确性。 可选地， 在上述实施例中， 在步骤 102之后还包括为重批话单增加话单字 段， 在将重批话单挑选到重批话单组后， 为重批话单组增加标识， 所述重批 话单组的标识作为给重批话单增加的第一个话单字段， 在重批话单组内按照 业务发生的先后顺序给重批话单编号， 所述重批话单组内重批话单的编号作 为给重批话单增加的第二个话单字段。 对于共用账户下的重批话单被挑选到重批话单组后， 还包括， 进一步按 照用户所在的网络节点和重批话单的时间先后顺序， 将重批话单挑选到微重 批话单组中， 因为不同的网络节点的接收速度不同， 在重批时可能因为第一 网络节点产生的重批话单重批速度较快， 业务发生在前的第二网络节点的重 批话单还没重批完成， 就已经开始重批下一个在第一网络节点产生的重批话 单， 造成计费重批错误， 所以需要将共用账户下的重批话单挑选到微重批话 单组中才能保证计费的准确性。 在将重批话单挑选到微重批话单组时还可以为微重批话单组编号， 作为 给微重批话单组内的话单增加的第三个话单字段， 在微重批话单组内还可以 进一步给重批话单案时间的先后顺序编号， 作为给重批话单增加的第四个话 单字段， 微重批话单组内的重批话单重批时， 按照微重批话单组的编号顺序 依次重批， 第一个微重批话单组重批完成后才会对第二个微重批话单组进行 重批， 而且在重批话单组内的所有重批话单组重批完成后， 才会作为一个事 务， 统一提交， 若在重批到任意一条话单时， 发生重批错误， 要结束对该重 批话单组的重批操作， 所有重批话单组中的重批话单将统一进行回滚， 再重 复上述 ^兆单过程， 再次进行重批， 以保证重批计费的准确性。 无论是共用账户下扣费的重批话单还是在单用户账户下扣费的重批话 单， 都要增加业务类型的话单字段， 以确保在重批时可以准确区分不同的业 务应该变动的费用， 这样在重批时， 就根据业务类型确定， 重批不同的业务 对应的不同的变动费用， 根据不同的变动费用， 对重批话单进行重批， 这样 就可以保证重批后每种业务类型的话单计费的准确性。 为便于理解， 下面以一具体的应用场景对上述实施例中描述的计费重批 的方法进行详细描述， 具体的： 手机计费*** 2011-1-1 00:00:00到 2011-1-1 01 :00:00计费错误， 要求对于 个人付费的收费业务， 每次业务需加收 0.5角附加费。 用户 12000000000定购 某套餐： 当月话音业务消费满 100分钟，赠送当月短信 10条，该用户在 2011-1-1 00:00:00话音业务消费累计达 99分钟， 00:01 :00发起话音业务 2分钟，付费 2角， 00: 00: 05发起短信业务一条， 付费 0.5角， 00: 03: 05发起短信业务 1条， 免费， 00: 04: 00发起 GPRS业务 600秒，付费 1角。用户 12000000002在 2011-1-1 00: 01 : 02发起话音业务 121秒， 付费 3角。 用户 12800000000、 12900000002 同属远天集团， 但分别部署在 CBS101、 CBS102两个网络节点， 远天集团代 成员付费共 1000 ¥ , 远天集团在 2011-1-1 00:00:00时已付费 998 ¥ , 用户 12800000000在 00:01 :00发起呼叫 600秒， 由远天集团代付费 10角； 用户
12900000002在 00:01 :10发起呼叫 630秒， 由远天集团代付费 10角， 自己付费 1 角； 用户 12900000002在 00: 14:10发起呼叫 630秒， 自己付费 11角； 用户
12800000000在 00:15:00发起呼叫 660秒， 自己付费 11角。 该时间段内计费的用户的话单均需要重批， 重批话单格式如下： 话音业务话单， 格式：
call-typelcharging-numberlother-partylstart-timelend-timeldurationlfee。
短信业务话单， 格式：
call-typelcharging-numberlother-partylsend-timel traffic Ifee
GPRS业务话单， 格式：
call-typelcharging-numberlstart-timelend-timel durationltraffic Ifee
其中： call-type, 呼叫类型， 00-主叫; 01-被叫;
Charging-number, 计费方号码； Other-party, 对方号码；
start-time, 业务开始时间； send-time, 发送时间； end-time, 业务结束时 间； duration, 时长， 单位秒； traffic, 流量， 单位字节； fee, 费用， 单位角。 集团业务的重批话单格式个人业务的重批话单的尾部增加一个字段 share-fee。 其中， fee表示自身账户付费结果； share-fee表示集团代付费结果。
重批方法如下： 按照错误发生的时间 2011-1-1 00:00:00到 2011-1-1 01 :00:00选择重批话 单， 选择的重批话单有：
00I12000000000I12000000001I20110101000100I20110101000300I120I2; 00I12000000000I12000000001I20110101000005I100I0.5
00I12000000000I12000000001I20110101000305I120I0
0011200000000012011010100040012011010100100016001409611 ;
00I12800000000I12000000001I20110101000100I20110101001000I600I0I10
00112800000000112000000001120110101001500120110101002600166011110
00112900000002112000000003120110101000110120110101001040163011110
00112900000002112000000003120110101001410120110101002440163011110 在上述选择到得重批话单中， 按照第一付费账号的不同， 将同一付费账 号下的重批话单挑选的同一个重批话单组中， 挑选后为：
远天集团的付费账号下的重批话单组内的重批话单有：
00112800000000112000000001120110101000100120110101001000160010110
00112800000000112000000001120110101001500120110101002600166011110
00112900000002112000000003120110101000110120110101001040163011110
00112900000002112000000003120110101001410120110101002440163011110 用户 12000000000付费账号下的重批话单组内的重批话单有：
00I12000000000I12000000001I20110101000100I20110101000300I120I2; 00I12000000000I12000000001I20110101000005I100I0.5
00I12000000000I12000000001I20110101000305I120I0
0011200000000012011010100040012011010100100016001409611 ο
将上述远天集团账户下的重批话单挑选到远天集团重批话单组后，还进 一步将远天集团重批话单组内的重批话单挑选到微重批话单组中， 因为远天 集团下的两个用户 12800000000和 12900000002分别部署在 CBS101、 CBS102 网络节点， 按照网络节点和话单业务时间的先后顺序将远天集团重批话单组 内的重批话单按顺序挑选到不同的微重批话单组内； 在挑选对远天集团账户下的重批话单时还包括将重批话单增加话单字 段， 在将重批话单挑选到重批话单组后， 为重批话单组增加标识， 所述重批 话单组的标识作为给重批话单增加的第一个话单字段， 在重批话单组内按照 业务发生的先后顺序给重批话单编号， 所述重批话单组内重批话单的编号作 为给重批话单增加的第二个话单字段， 增加的第个字段表示重批话单在重批 话单组中的顺序编号， 0表示第一条， 999999表示最后一条， 在将重批话单组 内的重批话单挑选到微重批话单组时还要为微重批话单组编号， 作为第三个 字段， 在微重批话单组内为重批话单按照时间先后顺序编号， 0表示第一条， 999999表示最后一条， 增加的最后一个话单字段为业务类型。 远天集团下重批话单组中的微重批话单组中的重批话单分别为； 第一微重批话单组中为在 CBS101网络节点的用户的重批话单：
1I0I1I999999IVOICEI00I12000000000I12000000001I20110101000100I201 10101001000160010110;
第二微重批话单组中为在 CBS102网络节点用户的重批话单：
1I1I2I0IVOICEI00I12900000002I12000000003I20110101000110I20110101 001040163011110;
1I2I2I999999IVOICEI00I12900000002I12000000003I20110101001410I201 10101002440163011110;
第三微重批话单组中为在 CBS101网络节点的用户的重批话单：
1I999999I3I999999IVOICEI00I12000000000I12000000001I2011010100150 0120110101002600166011110。
用户 12000000000的重批话单组内的重批话单增加话单字段后为，第一位 表示重批话单组的编号， 第二位表示重批话单在重批话单组中的顺序编号， 0 表示第一条， 999999表示最后一条，第三位表示业务类型，话音、短信或 GPRS, 增加字段后的重批话单为：
1I0ISMSI00I12000000000I12000000001I20110101000005I100I0.5;
1I1IVOICEI00I12000000000I12000000001I20110101000100I20110101000 300112012;
1I2ISMSI00I12000000000I12000000001I20110101000305I120I0;
1I999999IGPRSI00I12000000000I20110101000400I20110101001000I600I4
09611 ;
在本应用场景是对个人付费的收费业务， 每次业务需加收 0.5角附加费。 重批后， 远天集团重批话单组内重批后的话单为：
第一微重批话单组中的重批话单为：
1I0I1I999999IVOICEI00I12000000000I12000000001I20110101000100I201 10101001000160010110;
第二微重批话单组中的重批话单为：
1I1I2I0IVOICEI00I12900000002I12000000003I20110101000110I20110101 001040163011.5110;
1I2I2I999999IVOICEI00I12900000002I12000000003I20110101001410I201 101010024401630111.510;
第三微重批话单组中的重批话单为：
1I999999I3I999999IVOICEI00I12000000000I12000000001I2011010100150 01201101010026001660111.510;
上述三个微重批话单组在对各自话单组内的重批话单的重批是作为一个 事务来完成的， 只有第一微重批话单组重批完后， 才会对第二微重批话单组 进行重批， 接下来是第三微重批话单组， 只有在三个微重批话单组中的重批 话单都重批完后才会结束该事务， 统一进行提交， 如果重批的过程中， 有一 个重批话单的重批出现错误， 三个微重批话单组中的重批话单将统一进行回 滚， 再重复上述挑单排序过程， 再次进行重批， 以保证重批计费的准确性。
用户 12000000000重批话单组内的重批后的话单为：
1I0ISMSI00I12000000000I12000000001I20110101000005I100I1 ;
1I1IVOICEI00I12000000000I12000000001I20110101000100I20110101000 300112012.5;
1I2ISMSI00I12000000000I12000000001I20110101000305I120I0;
1I999999IGPRSI00I12000000000I20110101000400I20110101001000I600I4 09611.5;
对第二话单文件的第一话单组内的重批话单的重批也是作为一个事务来 完成的， 只有第一话单组内的所有重批话单都重批完后才会统一提交， 如果 重批的过程中， 有一个重批话单的重批出现错误， 第二重批话单组内的所有 重批话单将统一进行回滚， 再重复上述挑单排序过程， 再次进行重批， 以保 证重批计费的准确性。
在本应用场景中， 将远天集团下不同节点的用户的重批话单分到同一个 重批话单组中， 将一个用户多种业务的重批话单分到一个重批话单组中， 在 各自的重批话单组中按照业务发生时间的先后对重批话单进行重批， 与现有 技术中按照业务类型或者不同节点将重批话单挑选到不同的话单文件中相 比，本发明实施例不会出现同一个集团下因先重批 CBS101节点，导致 CBS102 节点上用户虽然发起业务的时间在 CBS101节点上用户之前，但还是要个人付 费的状况发生， 也不会出现同一个用户因先对话音业务进行了重批， 导致在 还没有免费短信时发起的短信业务也享受了免费服务， 保证了重批后计费的 准确性。 下面介绍本发明实施例中的计费重批的装置实施例， 请参阅图 2, 本发 明实施例中的计费重批的装置包括：
挑单单元 201 , 按照第一付费账户的不同， 将计费错误发生时间内的同一 个第一付费账户的重批话单挑选到同一个重批话单组中， 所述第一付费账户 是指在付费时被优先扣费的账户。
重批单元 202, 用于对重批话单组内的重批话单， 按照业务发生时间的先 后顺序重批， 并在重批话单组内的所有重批话单重批完成后， 将所述重批话 单组内的重批后的话单统一提交给账务***。
本实施例中， 挑单单元 201按照第一付费账户的不同， 将计费错误发生时 间内的同一个第一付费账户的重批话单挑选到同一个重批话单组中， 重批单 元 202按照业务发生时间的先后顺序， 对重批话单进行重批。 本发明实施例提 供的重批装置与现有技术相比， 本发明实施例采用将满足同一第一付费账号 的所有重批话单挑选到同一个重批话单组中了， 在同一个重批话单组中按照 重批话单对应业务发生时间的先后顺序对重批话单组中的所有话单进行重 批， 保证了重批后计费的准确性。
参阅图 3 , 本发明实施例中的计费重批装置还包括：
话单字段增加单元 302, 用于所述在将重批话单挑选到重批话单组或 /和 微重批话单组时， 对重批话单增加话单字段；
在所述挑单单元 301将重批话单挑选到重批话单组时，话单字段增加单元 302按照挑选完成的先后顺序将重批话单组增加标识，所述重批话单增加的话 单字段为重批话单组的标识；
在所述挑单单元 301将所述重批话单挑选到重批话单组后，话单字段增加 单元 302再按照业务发生时间的先后，对每个重批话单组内的重批话单按顺序 编号， 所述话单字段增加单元为重批话单增加的第二个话单字段为重批话单 组内的重批话单的顺序编号， 所述重批单元重批时按照话单的顺序编号进行 重批；
按照节点和重批话单业务发生时间的先后，所述挑单单元 301将重批话单 组内的重批话单挑选到微重批话单组时，话单字段增加单元 302按照挑选完成 的先后顺序将微重批话单组编号， 所述话单字段增加单元为共用账户下的重 批话单增加的第三个字段为微重批话单组的编号， 所述微重批单元重批时按 照微重批话单组的编号顺序依次重批。
所述重批单元 303还进一步包括多个微重批单元 3031 , 所述微重批单元
3031 , 用于按照微重批话单组内重批话单对应业务的发生时间的先后进行串 行重批， 并且在所有微重批话单组中的重批话单全部重批完成后统一提交。
结束单元 304, 用于在重批单元 303重批所述重批话单组内的任意一条重 批话单时， 发生重批错误时， 结束所述重批话单组的重批操作。
所述结束单元 304,进一步用于在所述微重批单元 3031重批任意一条重批 话单时， 发生重批错误时， 结束所述微重批话单组的重批操作。
本实施例中， 在挑单单元 301将重批话单挑选到重批话单组和 /或微重批 话单组时， 话单字段增加单元 302为重批话单增加话单字段， 重批单元 303或 微重批单元 3031重批时， 按照重批话单组或微重批话单组内重批话单业务发 生时间的先后顺序重批， 保证了重批后计费的准确性。
本发明实施例中， 计费重批装置可以包括多个重批单元， 每个重批单元 也可以包括多个微重批单元， 为便于理解， 对应于本发明实施例中的方法实 施例的应用场景， 介绍本发明实施例的计费重批装置。
参阅图 4, 本发明实施例的计费重批的装置 40包括：
重批单元 401 , 用于重批远天集团账户下的所有业务的重批话单； 重批单元 402, 用于重批用户 12000000000多种业务的重批话单； 所述重批单元 401包括微重批单元 4011 , 微重批单元 4012和微重批单元
4013;
所述微重批单元 4011 , 用于重批第一微重批话单组中的重批话单； 所述微重批单元 4012, 用于重批第二微重批话单组中的重批话单； 所述微重批单元 4013 , 用于重批第三微重批话单组中的重批话单； 重批时重批单元 401内的微重批单元 4011 ,微重批单元 4012和微重批单元 4013之间是按照从微重批单元 4011到微重批单元 4013的顺序重批的， 第二重 批单元 402中的重批话单也是按照业务发生时间的先后顺序重批的，保证了重 批计费的准确性， 重批单元 401 , 重批单元 402间是并行重批的， 提高了计费 重批的速度。 本应用场景只给出了很少的重批话单， 但在实际工作中， 会有 很多重批话单， 计费重批装置也不限于只有两个重批单元， 可以根据实际重 批话单的多少， 启动多个重批单元， 当然， 共用账户下的重批单元中也可以 有多个微重批单元。 本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步 骤是可以通过程序来指令相关的硬件来完成， 该程序可以存储于一计算机可 读存储介质中， 存储介质可以包括： ROM、 RAM, 磁盘或光盘等。
以上对本发明实施例所提供的计费重批的方法以及计费重批的装置进行了 以上实施例的说明只是用于帮助理解本发明的方法及其核心思想； 同时， 对 于本领域的一般技术人员， 依据本发明的思想， 在具体实施方式及应用范围 上均会有改变之处， 综上所述， 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要 求
1、 一种计费重批的方法， 其特征在于， 包括：
按照第一付费账户的不同， 将计费错误发生时间内的同一个第一付费账 户的重批话单挑选到同一个重批话单组中， 所述第一付费账户是指在付费时 被优先扣费的账户；
对重批话单组内的重批话单， 按照业务发生时间的先后顺序重批， 并在 重批话单组内的所有重批话单重批完成后， 将所述重批话单组内的重批后的 话单统一提交给账务***。
2、 根据权利要求 1所述的计费重批的方法， 其特征在于， 还包括： 在重批所述重批话单组内的任意一条重批话单时， 发生重批错误时， 结 束所述重批话单组的重批操作。
3、 根据权利要求 1或 2所述的计费重批的方法， 其特征在于， 所述第一付 费账户包括单用户账户或多用户共用账户中的一个或两个， 所述单用户账户 为所述计费错误发生时间内发生多种业务的单个用户的账户， 所述多用户共 用账户为多个用户共用一个账户。
4、 根据权利要求 3所述的计费重批的方法， 其特征在于， 还包括： 当所述共用账户下的用户所发生的业务产生的重批话单， 既有共用账户 下的重批话单又有单用户账户下的重批话单时；
将满足所述共用账户的重批话单优先挑选到共用账户的重批话单组中； 在剩余的重批话单中， 将满足所述单用户账户的重批话单挑选到所述单 用户账户的重批话单组中。
5、 根据权利要求 3所述的计费重批的方法， 其特征在于， 还包括： 在所述第一付费账户是多用户共用账户的重批话单组内， 根据用户所在 的网络节点， 并按照重批话单对应的业务的发生时间的先后将重批话单挑选 到微重批话单组中；
不同微重批话单组间， 按照微重批话单组内重批话单对应业务的发生时 间的先后进行串行重批， 并且在所有微重批话单组中的重批话单全部重批完 成后统一提交。
6、 根据权利要求 5所述的计费重批的方法， 其特征在于， 所述在将重批 话单挑选到重批话单组或 /和微重批话单组时还包括：
对重批话单增加话单字段；
在将重批话单挑选到重批话单组时， 按照挑选完成的先后顺序将重批话 单组增加标识， 所述重批话单增加的话单字段为重批话单组的标识；
再按照业务发生时间的先后， 对每个重批话单组内的重批话单按顺序编 号， 所述重批话单增加的第二个话单字段为重批话单组内的重批话单的顺序 编号， 重批时按照话单的顺序编号进行重批；
按照节点和重批话单业务发生时间的先后， 将重批话单组内的重批话单 挑选到微重批话单组时， 按照挑选完成的先后顺序将微重批话单组编号， 所 述共用账户下的重批话单增加的第三个字段为微重批话单组的编号， 重批时 按照微重批话单组的编号顺序依次重批。
7、 根据权利要求 6所述的计费重批的方法， 其特征在于， 还包括 对单用户账户的重批话单组内的重批话单增加业务类型的话单字段， 重 批时根据业务类型确定重批话单的变动费用；
对共用账户下的微重批话单组内的重批话单增加的业务类型的话单字 段， 重批时根据业务类型确定重批话单的变动费用。
8、 一种计费重批的装置， 其特征在于， 包括：
挑单单元， 按照第一付费账户的不同， 将计费错误发生时间内的同一个 第一付费账户的重批话单挑选到同一个重批话单组中， 所述第一付费账户是 指在付费时被优先扣费的账户；
重批单元， 用于对重批话单组内的重批话单， 按照业务发生时间的先后 顺序重批， 并在重批话单组内的所有重批话单重批完成后， 将所述重批话单 组内的重批后的话单统一提交给账务***。
9、 根据权利要求 8所述的计费重批的装置， 其特征在于， 还包括： 结束单元， 用于在重批所述重批话单组内的任意一条重批话单时， 发生 重批错误时， 结束所述重批话单组的重批操作。
10、 根据权利要求 8或 9所述的计费重批的装置， 其特征在于， 所述第一 付费账户包括单用户账户或多用户共用账户中的一个或两个， 所述单用户账 户为所述计费错误发生时间内发生多种业务的单个用户的账户， 所述多用户 共用账户为多个用户共用一个账户。
11、 根据权利要求 10所述的计费重批的装置， 其特征在于， 包括： 当所述共用账户下的用户所发生的业务产生的重批话单， 既有共用账户 下的重批话单又有单用户账户下的重批话单时， 所述挑单单元进一步用于： 将满足所述共用账户的重批话单优先挑选到一个重批话单组中； 在剩余的重批话单中， 将满足所述单用户账户的重批话单挑选到另一个 重批话单组中。
12、 根据权利要求 10所述的计费重批的装置， 其特征在于， 包括： 所述挑单单元， 进一步用于在所述第一付费账户是多用户共用账户的重 批话单组内， 根据用户所在的网络节点， 并按照重批话单对应的业务的发生 时间的先后将重批话单挑选到微重批话单组中；
所述重批单元进一步包括一个或一个以上微重批单元， 所述微重批单元 用于按照微重批话单组内重批话单对应业务的发生时间的先后进行串行重 批， 并且在所有微重批话单组中的重批话单全部重批完成后统一提交。
13、 根据权利要求 12所述的计费重批的装置， 其特征在于， 包括： 话单字段增加单元， 用于所述在将重批话单挑选到重批话单组或 /和微重 批话单组时， 对重批话单增加话单字段；
在所述挑单单元将重批话单挑选到重批话单组时， 所述话单字段增加单 元按照挑选完成的先后顺序将重批话单组增加标识， 所述重批话单增加的话 单字段为重批话单组的标识；
在所述挑单单元将所述重批话单挑选到重批话单组后， 所述话单字段增 加单元再按照业务发生时间的先后， 对每个重批话单组内的重批话单按顺序 编号， 所述话单字段增加单元为重批话单增加的第二个话单字段为重批话单 组内的重批话单的顺序编号， 所述重批单元重批时按照话单的顺序编号进行 重批；
按照节点和重批话单业务发生时间的先后， 所述挑单单元将重批话单组 内的重批话单挑选到微重批话单组时， 按照挑选完成的先后顺序将微重批话 单组编号， 所述话单字段增加单元为共用账户下的重批话单增加的第三个字 段为微重批话单组的编号， 所述微重批单元重批时按照微重批话单组的编号 顺序依次重批
PCT/CN2012/076200 2011-06-08 2012-05-29 一种计费重批的方法及装置 WO2012167702A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110152502.2A CN102821379B (zh) 2011-06-08 2011-06-08 一种计费重批的方法及装置
CN201110152502.2 2011-06-08

Publications (1)

Publication Number Publication Date
WO2012167702A1 true WO2012167702A1 (zh) 2012-12-13

Family

ID=47295468

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/076200 WO2012167702A1 (zh) 2011-06-08 2012-05-29 一种计费重批的方法及装置

Country Status (2)

Country Link
CN (1) CN102821379B (zh)
WO (1) WO2012167702A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105451357B (zh) * 2014-09-26 2019-01-22 中国电信股份有限公司 一种话单调度方法和***
TWI628607B (zh) * 2015-04-01 2018-07-01 中華電信股份有限公司 Accounting processing notice billing re-validation method and system
CN106330509B (zh) * 2015-06-30 2019-11-26 华为技术有限公司 一种计费重批的方法和装置
CN108898473A (zh) * 2018-06-14 2018-11-27 中国铁塔股份有限公司 一种项目转资方法及装置
CN112838932A (zh) * 2019-11-25 2021-05-25 ***通信集团浙江有限公司 基于按量累积批价的重批价方法、装置及计算设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101645782A (zh) * 2009-02-10 2010-02-10 中国科学院声学研究所 一种基于用户业务量的在线计费方法及***
CN101938362A (zh) * 2009-06-29 2011-01-05 华为技术有限公司 计费重批的方法、装置及***
CN102075641A (zh) * 2009-11-25 2011-05-25 ***通信集团甘肃有限公司 一种业务话单的处理方法和装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101594601B (zh) * 2008-05-30 2012-04-04 华为技术有限公司 计费方法、装置及***

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101645782A (zh) * 2009-02-10 2010-02-10 中国科学院声学研究所 一种基于用户业务量的在线计费方法及***
CN101938362A (zh) * 2009-06-29 2011-01-05 华为技术有限公司 计费重批的方法、装置及***
CN102075641A (zh) * 2009-11-25 2011-05-25 ***通信集团甘肃有限公司 一种业务话单的处理方法和装置

Also Published As

Publication number Publication date
CN102821379B (zh) 2015-03-11
CN102821379A (zh) 2012-12-12

Similar Documents

Publication Publication Date Title
US20170142263A1 (en) System and method for monitoring account usage on a platform
WO2012167702A1 (zh) 一种计费重批的方法及装置
KR20120061807A (ko) 수익 배당을 갖는 엔티티 마다 과금 데이터를 생성하는 프론트 엔드 과금 시스템
WO2011127296A1 (en) Facilitating billing of embedded applications
WO2010105528A1 (zh) 在线计费方法、装置和***
CN102144372A (zh) Ims网络中的联机计费关联
JP2004515168A (ja) 個人の識別番号を請求するプロフェッショナルサービス
WO2012167676A1 (zh) 通信设备的通话付费处理方法和***
US10944874B2 (en) Telecommunication system for monitoring and controlling of a network providing resource to a user
WO2009143746A1 (zh) 计费方法、计费***及计费装置
WO2019101082A1 (zh) 一种增值业务的实现方法、装置和行业应用鉴权中心
US9008614B2 (en) Method, device and computer program product for controlling use of electronic communication services
US9838862B2 (en) Mobile digital cellular telecommunication system with advanced functionality for rating correction
WO2011144089A2 (zh) 一种费用重批方法以及相关装置
WO2011140891A1 (zh) 预付费计费的方法、装置及***
WO2016192441A1 (zh) 扣费方法及***
EP3331196B1 (en) Telecommunication system for monitoring and controlling of a network providing resource to a user
CN104363570A (zh) 一种基于通信帐户以整月为周期的按次代缴付费方法
CN102131174B (zh) 预付费计费的方法、装置及***
EP2950514B1 (en) Mobile digital cellular telecommunication system with advanced rating functionality
CN105141432A (zh) 云服务订单处理方法与装置
US9264557B2 (en) Charging systems and methods for telecommunications
TWI405452B (zh) Immediate Pricing and Immediate Charge Method
KR102292328B1 (ko) 단말기 할부 청구금액 산정 시스템 및 그 제어방법과, 그 제어방법을 실행하기 위한 프로그램을 기록한 기록 매체와, 하드웨어와 결합되어 그 제어방법을 실행시키기 위하여 매체에 저장된 애플리케이션
EP3091764B1 (en) Mobile digital cellular telecommunication system with advanced flexible rating functionality

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

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

Country of ref document: EP

Kind code of ref document: A1