CN110662188B - Charging method and system - Google Patents

Charging method and system Download PDF

Info

Publication number
CN110662188B
CN110662188B CN201810682632.9A CN201810682632A CN110662188B CN 110662188 B CN110662188 B CN 110662188B CN 201810682632 A CN201810682632 A CN 201810682632A CN 110662188 B CN110662188 B CN 110662188B
Authority
CN
China
Prior art keywords
data
charging
static data
ticket
static
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201810682632.9A
Other languages
Chinese (zh)
Other versions
CN110662188A (en
Inventor
陈娜
刘智琼
张金娟
丘晖
刘斌
华竹轩
俞科峰
伍运珍
池炜成
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp 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 China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN201810682632.9A priority Critical patent/CN110662188B/en
Publication of CN110662188A publication Critical patent/CN110662188A/en
Application granted granted Critical
Publication of CN110662188B publication Critical patent/CN110662188B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Meter Arrangements (AREA)

Abstract

The invention provides a charging method and a system, wherein the method comprises the following steps: acquiring all static data corresponding to the call ticket, and combining the static data and the call ticket; wherein, the static data does not need to be modified in the charging process; performing charging processing based on the static data conversation list to obtain dynamic accumulated data corresponding to the ticket; and generating a charging bill corresponding to the bill according to a preset charging bill generation rule and based on the static data and the dynamic accumulated data. The charging method and the charging system realize application and data decoupling in charging, can obtain all static data required by the ticket once after receiving the ticket, greatly reduce the network interaction between nodes after cloud processing, reduce the processing complexity and improve the overall efficiency of the system.

Description

Charging method and system
Technical Field
The present invention relates to the field of charging technologies, and in particular, to a charging method and system.
Background
The IT system of an enterprise has not only computation-intensive scientific engineering calculations, but also numerous Web and transactional applications that frequently read and write I/O. Most program systems are called as compute intensive when computation, logic judgment and circulation result in high CPU and memory occupancy rates. The billing system of the telecom operator is a typical calculation intensive application, and needs to combine the package situation ordered by the user and the detailed information in the call ticket to perform a large amount of complex fee calculation and preferential treatment on the call ticket of the user, so as to finally obtain the consumption data of the user.
With the development of 4G service scale, the traffic ticket increases rapidly, higher requirements are put on the processing performance of the charging system, and the traditional IT architecture is imperative to be transformed to a distributed and elastic cloud architecture. In order to perform distributed processing, the charging system needs to split the computation logic of the original service requirement, and disperse the split computation logic to each computation node. However, the existing distributed charging architecture has the following problems: due to the cloud transformation of the charging system, data access and calculation logic which are originally completed only in a small-sized machine memory are split to each dispersed node, the calculation fee processing of each ticket needs multiple network interaction, and the charging processing efficiency is greatly reduced through frequent network transmission.
Disclosure of Invention
One or more embodiments of the present invention provide a charging method and system.
According to an aspect of the present disclosure, there is provided a charging method, including: acquiring all static data corresponding to the call ticket, and combining the static data and the call ticket; wherein, the static data does not need to be modified in the charging process; performing charging processing on the call ticket based on the static data to obtain dynamic accumulated data corresponding to the call ticket; and generating a charging bill corresponding to the bill according to a preset charging bill generation rule and based on the static data and the dynamic accumulated data.
Optionally, the acquiring all static data corresponding to the ticket, and the combining the static data and the ticket includes: acquiring a charging processing rule corresponding to the ticket; and performing charging preprocessing on the call ticket based on the charging processing rule, and determining all static data required by calculating the call ticket.
Optionally, sending the static data and the ticket after the combination processing to at least one computing node for charging operation; and the ticket carries all the static data.
Optionally, the sending the static data and the ticket after the combination processing to at least one computing node for performing charging operation includes: acquiring resource consumption data of a plurality of computing nodes; wherein the resource consumption data comprises: CPU occupancy rate and memory occupancy rate; selecting at least one computing node with lowest resource consumption data from the plurality of computing nodes; sending the static data and the call ticket to the at least one computing node for charging processing, so as to generate the dynamic accumulated data; wherein the compute node comprises: and (4) cloud computing nodes.
Optionally, the generating a charging bill corresponding to the bill according to a preset charging bill generating rule and based on the static data and the dynamic accumulated data includes: receiving the dynamic accumulated data sent by a plurality of computing nodes; performing a closing process on the plurality of dynamic accumulated data to obtain an accumulated cost corresponding to the ticket; and generating the billing bill based on the accumulated cost and the static data.
Optionally, the computing node obtains benefit policy information according to the product charging type corresponding to the ticket, the charging start use time and the charging end time, and generates the charging bill according to the benefit policy information, the accumulated cost and the static data.
Optionally, the static material data and the dynamic accumulation data are stored in the first data storage device and the second data storage device respectively.
Optionally, the first data storage device and the second data storage device are both cloud database devices.
According to another aspect of the present disclosure, there is provided a charging system including: the static data acquisition module is used for acquiring all static data corresponding to the call ticket and combining the static data and the call ticket; wherein, the static data does not need to be modified in the charging process; the dynamic data obtaining module is used for carrying out charging processing on the call ticket based on the static data to obtain dynamic accumulated data corresponding to the call ticket; and the charging bill generation module is used for generating a charging bill corresponding to the bill according to a preset charging bill generation rule and based on the static data and the dynamic accumulated data.
Optionally, the static data obtaining module is configured to obtain a charging processing rule corresponding to the ticket; and performing charging preprocessing on the call ticket based on the charging processing rule, and determining all static data required by calculating the call ticket.
Optionally, the dynamic data obtaining module is configured to send the static data and the ticket after the combination processing to at least one computing node for performing charging operation; and the ticket carries all the static data.
Optionally, the dynamic data obtaining module is configured to obtain resource consumption data of a plurality of computing nodes; wherein the resource consumption data comprises: CPU occupancy rate and memory occupancy rate; selecting at least one computing node with lowest resource consumption data from the plurality of computing nodes; sending the static data and the call ticket to the at least one computing node for charging processing, so as to generate the dynamic accumulated data; wherein the compute node comprises: and (4) cloud computing nodes.
Optionally, the billing bill generation module is configured to receive the dynamically accumulated data sent by a plurality of computing nodes; performing a closing process on the plurality of dynamic accumulated data to obtain an accumulated cost corresponding to the ticket; and generating the billing bill based on the accumulated cost and the static data.
Optionally, the charging bill generating module is configured to obtain preference policy information according to a product charging type corresponding to the ticket, a charging start time and a charging end time, and generate the charging bill according to the preference policy information, the accumulated cost, and the static data.
Optionally, the data storage module is configured to store the static data and the dynamic accumulated data in the first data storage device and the second data storage device, respectively.
Optionally, the first data storage device and the second data storage device are both cloud database devices.
According to still another aspect of the present disclosure, there is provided a charging system including: a memory; and a processor coupled to the memory, the processor configured to perform the charging method described above based on instructions stored in the memory.
According to yet another aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon computer program instructions which, when executed by one or more processors, implement the steps of the method as described above.
The charging method and the charging system obtain all static data corresponding to the call ticket, combine the static data with the call ticket, perform charging processing based on a static data dialogue ticket, obtain dynamic accumulated data corresponding to the call ticket and generate a charging bill according to the static data and the dynamic accumulated data; the application and data decoupling in charging is realized, all static data required by the ticket can be obtained once after the ticket is received, the network interaction between the nodes after the cloud is greatly reduced, the processing complexity is reduced, and the overall efficiency of the system is improved.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without inventive exercise.
Fig. 1 is a flow diagram of one embodiment of a charging method according to the present disclosure;
fig. 2 is a schematic flow chart diagram of another embodiment of a charging method according to the present disclosure;
FIG. 3 is a block diagram of one embodiment of a billing system according to the present disclosure;
fig. 4 is a block diagram of another embodiment of a billing system according to the present disclosure.
Detailed Description
The present disclosure now will be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the disclosure are shown. The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
Fig. 1 is a flowchart illustrating an embodiment of a charging method according to the present disclosure, as shown in fig. 1:
step 101, acquiring all static data corresponding to the call ticket, combining the static data and the call ticket, and attaching all static data to the call ticket to become a part of the call ticket. The static data is not required to be modified in the charging process, and is static data.
And 102, carrying out charging processing based on the static data dialogue list to obtain dynamic accumulated data corresponding to the phone bill, wherein the dynamic accumulated data is dynamic data.
And 103, generating a charging bill corresponding to the bill according to a preset charging bill generation rule and based on the static data and the dynamic accumulated data.
The charging method changes the mode of obtaining the static data in the charging process, can change the mode of obtaining the static data from the distributed memory for a plurality of times in the traditional charging process into the mode of obtaining the static data once before rating, and can attach all the static data obtained once to the ticket as a part of the ticket.
In one embodiment, the static profile data includes user profiles and the like, the user profiles including product specifications, sales product specifications, product instances, sales product instances, product instance to product instance relationships, sales product instance to sales product instance relationships, and the like. The data will not change after the user purchases the telecom sales (commonly called package), and is therefore static data. The dynamic accumulated data refers to data that dynamically changes as the user uses the telecommunication service, such as accumulated amount (e.g., domestic flow X megabytes) and balance (money on the user's account), etc.
The static material data and the dynamic accumulation data can be stored in the first data storage device and the second data storage device respectively. The first data storage device and the second data storage device can be cloud database devices, and the two types of data can be deployed in different cloud databases and are associated through business relations.
Dividing the data to be accessed for calculating the bill fee into static data and dynamic accumulated data, storing them separately, after receiving the bill, simulating the fee calculating process in the preprocessing, thus obtaining all the static data needed by the bill at one time, and distributing them to each calculating node together with the bill as a part of the bill for calculating the fee. And acquiring a charging processing rule corresponding to the call ticket, wherein the charging processing rule can be various, such as a specific charging rule for rating. And performing charging preprocessing on the call ticket based on the charging processing rule, and determining all static data required by the calculation of the call ticket.
The call ticket is a specific record of the user using the telecommunication service, for example, a voice call ticket corresponds to a voice service (call making), and a data call ticket corresponds to a data service (internet access). In the link of preprocessing the dialogue list, the dialogue list is processed by format regulation, repetition elimination and the like, so that user data, namely static data, is not involved, and only the phone bill is processed. The pricing link (calculating fee, i.e. calculating the amount of money on a ticket) needs to be combined with the user data to calculate the fee. In the pricing, the user instance ID is found through the user number in the call list, the sales instance ID is found through the user instance ID, the specification of the sales is found through the sales instance ID, the pricing plan of the sales is found through the specification of the sales, and therefore the cost of the call list is calculated.
In an embodiment, the static data and the ticket may be sent to at least one computing node for performing charging operation, where the ticket may be tickets of multiple users or multiple tickets of one user, the tickets carry all the static data, the computing node includes a cloud computing node and the like, the computing node may be a physical device under a cloud framework or a logic division in the physical device, and the computing node may perform operations such as a preprocessing node, a re-ordering node, a rating node and the like.
The charging system specifically forms a data cluster by using various data needed by service processing, such as a cloud database for storing various static data and dynamic data, and related data management nodes. The data to be accessed for calculating the bill fee are divided into static data and dynamic cumulant/balance data and stored separately, and the charging system obtains all the static data required by the bill once after receiving the bill, thereby greatly reducing the network interaction between the nodes after cloud processing and improving the overall efficiency of the charging system.
And acquiring resource consumption data of the plurality of computing nodes, wherein the resource consumption data comprises CPU occupancy rate, memory occupancy rate and the like. At least one computing node with the lowest resource consumption data is selected from the plurality of computing nodes. Place the call ticket into a state of low resource consumption (if the CPU is low and the memory is used less)
For example, the static data and the ticket are sent to the selected at least one computing node for charging processing, so as to generate the dynamic accumulated data.
And receiving the dynamic accumulated data sent by the plurality of computing nodes, performing account-closing processing on the plurality of dynamic accumulated data to obtain the accumulated cost corresponding to the ticket, and generating a charging bill based on the accumulated cost and the static data. For example, the fee of each ticket is calculated and then the billing processing is carried out, the fees of the same type of the user are accumulated to obtain the real-time fee of the user, and the actions such as reminding, signal control and the like are conveniently carried out on the user. For example, the local telephone charge of a certain original user is 30 yuan, the telephone bill charge is 2 yuan after a telephone bill is processed, and the local telephone charge of the user is 32 yuan after the telephone bill is combined.
Fig. 2 is a flowchart illustrating another embodiment of a charging method according to the present disclosure, as shown in fig. 2:
step 201, obtaining a charging processing rule corresponding to the ticket.
Step 202, performing charging preprocessing on the call ticket based on the charging processing rule, and determining all static data required by the calculation of the call ticket.
Step 203, sending the static data and the ticket to at least one computing node for charging operation, wherein the ticket carries all the static data.
Step 204, receiving the dynamic accumulated data sent by the plurality of computing nodes.
Step 205, the multiple dynamic accumulated data are subjected to the reconciliation processing to obtain the accumulated cost.
In step 206, a billing bill is generated based on the accumulated charges and the static data.
In one embodiment, the preferential policy information is obtained according to the product charging type corresponding to the ticket, the initial charging use time and the end time, and the charging bill is generated according to the preferential policy information, the accumulated cost and the static data. For example, the call ticket is a voice call ticket, and the preferential policy information is obtained according to the product charging type corresponding to the voice call ticket, the initial charging time and the final charging time, the preferential policy can be various, for example, the charge rate on holidays is reduced by 50%, and a charging bill is generated according to the preferential policy information, the accumulated charge and the static data.
In one embodiment, as shown in fig. 3, there is provided a billing system 30 comprising: a static data acquisition module 31, a dynamic data acquisition module 32, a billing generation module 33 and a data storage module 34. The static data acquisition module 31 acquires all static data corresponding to the call ticket, and combines the static data with the call ticket; wherein, the static data does not need to be modified in the charging process. The dynamic data obtaining module 32 performs charging processing based on the static data dialogue list to obtain dynamic accumulated data corresponding to the phone bill. The charging bill generation module 33 generates a charging bill corresponding to the bill based on the static data and the dynamic accumulated data according to a preset charging bill generation rule.
The static data obtaining module 31 obtains a charging processing rule corresponding to the ticket, performs charging preprocessing on the ticket based on the charging processing rule, and determines all static data required for calculating the ticket. The dynamic data obtaining module 32 sends the static data and the ticket to at least one computing node for charging operation; wherein, the ticket carries all static data. The data storage module 34 stores the static data and the dynamic accumulated data in the first data storage device and the second data storage device, respectively. The first data storage device and the second data storage device are both cloud database devices.
The dynamic data obtaining module 32 obtains resource consumption data of a plurality of computing nodes; wherein the resource consumption data comprises: CPU occupancy, memory occupancy, etc. The dynamic data obtaining module 32 selects at least one computing node with the lowest resource consumption data from the plurality of computing nodes, and sends static data and a ticket to the at least one computing node for charging processing to generate dynamic accumulated data; the computing nodes comprise cloud computing nodes and the like.
The charging bill generation module 33 receives the dynamic accumulated data sent by the plurality of computing nodes, performs billing processing on the plurality of dynamic accumulated data, obtains the accumulated cost corresponding to the ticket, and generates a charging bill based on the accumulated cost and the static data. The charging bill generation module 33 obtains the discount policy information according to the product charging type corresponding to the ticket, the charging initial use time and the charging end time, and generates a charging bill according to the discount policy information, the accumulated cost and the static data.
Fig. 4 is a block diagram of a charging system according to another embodiment of the disclosure. As shown in fig. 4, the apparatus may include a memory 41, a processor 42, a communication interface 43, and a bus 44. The memory 41 is used for storing instructions, the processor 42 is coupled to the memory 41, and the processor 42 is configured to execute the accounting method implemented above based on the instructions stored in the memory 41.
The memory 41 may be a high-speed RAM memory, a nonvolatile memory (NoN-volatile memory), or the like, and the memory 41 may be a memory array. The storage 41 may also be partitioned, and the blocks may be combined into virtual volumes according to certain rules. The processor 42 may be a central processing unit CPU, or an application Specific Integrated circuit asic, or one or more Integrated circuits configured to implement the disclosed billing methods.
In one embodiment, the present disclosure also provides a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and the computer instructions, when executed by a processor, implement the charging method according to any of the above embodiments.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, apparatus, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Thus far, the present disclosure has been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
The charging method and the charging system provided by the embodiment obtain all static data corresponding to the call ticket, combine the static data with the call ticket, perform charging processing based on the static data conversation ticket, obtain dynamic accumulated data corresponding to the call ticket, and generate a charging bill corresponding to the call ticket based on the static data and the dynamic accumulated data; the application and data decoupling in charging is realized, all static data required by the ticket can be obtained once after the ticket is received, the network interaction between the nodes after the cloud is greatly reduced, and the overall efficiency of the system is improved.
The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

Claims (8)

1. A charging method, comprising:
acquiring all static data corresponding to the call ticket, and combining the static data and the call ticket, wherein the processing method comprises the following steps:
acquiring a charging processing rule corresponding to the ticket; performing charging preprocessing on the call ticket based on the charging processing rule, and determining all static data required by calculating the call ticket;
wherein, the static data does not need to be modified in the charging process; obtaining static data at one time before pricing, wherein the static data comprises user data; sending the static data and the ticket after the combination processing to at least one computing node for charging operation; the ticket carries all the static data;
performing charging processing on the call ticket based on the static data to obtain dynamic accumulated data corresponding to the call ticket;
acquiring resource consumption data of a plurality of computing nodes; the resource consumption data includes: CPU occupancy rate and memory occupancy rate; selecting at least one computing node with lowest resource consumption data from the plurality of computing nodes; sending the static data and the call ticket to the at least one computing node for charging processing, so as to generate the dynamic accumulated data; the computing node includes: a cloud computing node;
generating a charging bill corresponding to the bill according to a preset charging bill generation rule and based on the static data and the dynamic accumulated data;
wherein the dynamic accumulated data sent by a plurality of computing nodes is received; performing a closing process on the plurality of dynamic accumulated data to obtain an accumulated cost corresponding to the ticket; generating the billing bill based on the accumulated charges and the static data, comprising:
and the computing node acquires preferential policy information according to the product charging type corresponding to the ticket, the initial charging use time and the ending time, and generates the charging bill according to the preferential policy information, the accumulated cost and the static data.
2. The method of claim 1, wherein,
and respectively storing the static data and the dynamic accumulated data in a first data storage device and a second data storage device.
3. The method of claim 2, wherein,
the first data storage device and the second data storage device are both cloud database devices.
4. A charging system, comprising:
the static data acquisition module is used for acquiring all static data corresponding to the call ticket and combining the static data and the call ticket; wherein, the static data does not need to be modified in the charging process; the static data acquisition module is used for acquiring a charging processing rule corresponding to the ticket; performing charging preprocessing on the call ticket based on the charging processing rule, and determining all static data required by calculating the call ticket;
static data is acquired at one time before pricing, and the static data comprises user data;
the dynamic data acquisition module is used for sending the static data subjected to the combination processing and the call ticket to at least one computing node for charging operation; the ticket carries all the static data; performing charging processing on the call ticket based on the static data to obtain dynamic accumulated data corresponding to the call ticket;
the dynamic data acquisition module acquires resource consumption data of a plurality of computing nodes; the resource consumption data includes: CPU occupancy rate and memory occupancy rate; selecting at least one computing node with lowest resource consumption data from the plurality of computing nodes; sending the static data and the call ticket to the at least one computing node for charging processing, so as to generate the dynamic accumulated data; the computing node includes: a cloud computing node;
the charging bill generation module is used for generating a charging bill corresponding to the bill according to a preset charging bill generation rule and based on the static data and the dynamic accumulated data;
the charging bill generation module is used for receiving the dynamic accumulated data sent by a plurality of computing nodes; performing a closing process on the plurality of dynamic accumulated data to obtain an accumulated cost corresponding to the ticket; generating the billing bill based on the accumulated cost and the static data;
and the charging bill generation module is used for obtaining discount strategy information according to the product charging type corresponding to the bill and the charging initial use time and the charging end time, and is used for generating the charging bill according to the discount strategy information, the accumulated cost and the static data.
5. The system of claim 4, wherein,
and the data storage module is used for respectively storing the static data and the dynamic accumulated data in a first data storage device and a second data storage device.
6. The system of claim 5, wherein,
the first data storage device and the second data storage device are both cloud database devices.
7. A charging system, comprising:
a memory; and a processor coupled to the memory, the processor configured to perform the method of any of claims 1-3 based on instructions stored in the memory.
8. A computer readable storage medium having stored thereon computer program instructions which, when executed by one or more processors, implement the steps of the method of any one of claims 1 to 3.
CN201810682632.9A 2018-06-28 2018-06-28 Charging method and system Active CN110662188B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810682632.9A CN110662188B (en) 2018-06-28 2018-06-28 Charging method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810682632.9A CN110662188B (en) 2018-06-28 2018-06-28 Charging method and system

Publications (2)

Publication Number Publication Date
CN110662188A CN110662188A (en) 2020-01-07
CN110662188B true CN110662188B (en) 2021-09-07

Family

ID=69026199

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810682632.9A Active CN110662188B (en) 2018-06-28 2018-06-28 Charging method and system

Country Status (1)

Country Link
CN (1) CN110662188B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113645050B (en) * 2020-05-11 2024-02-23 中国移动通信集团湖北有限公司 Large-traffic user ticket gradient merging method and device and computing equipment
CN114629734B (en) * 2022-03-14 2024-04-26 阿里巴巴(中国)有限公司 Method, device, system and storage medium for processing ticket

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238012A (en) * 2010-04-23 2011-11-09 华为技术有限公司 Charging method and system
CN102308604A (en) * 2011-07-07 2012-01-04 华为技术有限公司 Cluster on-line charge mode and device
CN105721174A (en) * 2016-04-25 2016-06-29 中国联合网络通信集团有限公司 Charging method, charging system and charging terminal

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100492975C (en) * 2007-03-28 2009-05-27 华为技术有限公司 Service charging method, system, network access server and protocol resolver
US20150134515A1 (en) * 2013-11-08 2015-05-14 Brian Cosgray Methods and systems for electronic payment of a consumer's bills
WO2016018440A1 (en) * 2014-08-01 2016-02-04 Hewlett-Packard Development Company, L.P. Billing consumption of cloud-based resources

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238012A (en) * 2010-04-23 2011-11-09 华为技术有限公司 Charging method and system
CN102308604A (en) * 2011-07-07 2012-01-04 华为技术有限公司 Cluster on-line charge mode and device
CN105721174A (en) * 2016-04-25 2016-06-29 中国联合网络通信集团有限公司 Charging method, charging system and charging terminal

Also Published As

Publication number Publication date
CN110662188A (en) 2020-01-07

Similar Documents

Publication Publication Date Title
CN107464151B (en) Order data processing method and device for high-concurrency service
CN110493016B (en) Flow service charging method and device
TW201800994A (en) Resource processing method and device
CN107358524B (en) Method for leveling funds among multiple account management lines in same currency
CN110233741B (en) Service charging method, device, equipment and storage medium
CN109598495A (en) Data processing method, device, server and computer readable storage medium
CN111260371A (en) Recommendation method and device for domestic service route, storage medium and electronic equipment
CN109996202B (en) Flow charging method and device
CN110458611A (en) Method, apparatus and calculating equipment for processing of fixing a price
CN111932238B (en) Payment account recommendation method and device and electronic equipment
CN111461763A (en) Resource allocation method and device
CN110188990A (en) A kind of resource request and funds request shunt method, device and equipment
CN110662188B (en) Charging method and system
CN111709777A (en) Payment mode recommendation method, system, terminal device and storage medium
CN106096926B (en) Event processing method, device, electronic device and storage medium
CN107886428B (en) Method for determining payment clearing exchange rate and payment clearing system
CN110489418B (en) Data aggregation method and system
CN111988749B (en) Dynamic tariff generation method and device
CN107688959B (en) Breakpoint list processing method, storage medium and server
CN106327273A (en) STS-based prepaid electricity selling system and method
CN1322706C (en) Method of realizing real time segmental charging
US20210385634A1 (en) Method of determining shared service index based on shared service of communication credential
CN111429125B (en) Account management method and device, storage medium and electronic equipment
CN113869891A (en) Optimization method and system for dynamic splitting of bill amount
CN109428732A (en) A kind of call bill processing method and equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant